Can you be more specific here? HTML and CSS can't be described like that in my opinion.
It is complex but not complicated. You can start with just a few small parts and get to a usable and clean document within hours from the first contact with the languages. The tags and rules are usually quite self-describing while consice and there are tons and tons of good docs and tools. The development of the standards is also open and you can peek there if you want to understand decisions and rationals.
You could say the existing browser vendors pushed to make the HTML standard more complicated to the point that there's no chance for a newcomer to compete with the existing ones.
Sure, technical documents are long but that still doesn’t support the original claim that they are “unnecessarily complex, bloated, convoluted” and it’s actually evidence against the assertion that they’re “difficult to implement without specific knowledge of its features”: most of why those are long documents is that they carefully detail how necessarily complex systems interact in sufficient detail to implement them whereas the Office XML specs at least historically had things like flags telling to behave like, say, Word95 without fully specifying the behaviour in question.
The original claim was clearly actually just an opinion; I don't think there's merit to treating it as a series of logical statements, or at intricate depth in general.
Evidence for this is in the very words used: unnecessary, complex, bloated, convoluted. These are very human terms that are thus subject to personal interpretation and opinions.
It shouldn't be surprising then that their "claim" thus fails scrutiny. All they actually meant to say is that HTML and CSS are both verbose standards with a lot of particularities - still something subjective, but I think page / word / character counts are pretty agreeable attributes to estimate this with in an objective way. Hence why I brought those up exactly.
Of course it’s an opinion: the point is that it’s neither persuasive nor internally inconsistent. They haven’t given any reason to believe they have enough domain knowledge to compare the two authoritatively. It’s also inconsistent to criticize OOXML for being difficult to implement without extra knowledge and then to criticize a truly open spec for being detailed enough to implement without extra – the entire HTML5 process was intended to reduce the number of cases where people were relying on things which required implementers to know how a specific engine like IE worked.
Sure the spec might be enormous but you don't need to touch it at all to be productive quickly. In no HTML or CSS tutorial i'v ever seen was a reference to the spec nor did i need to go there to solve something. And that in itself is another proof how nicely it is designed actually. Because on the other hand there are other document types or schemas where you absolutely have to go to the spec because it's is so cryptic and badly designed and not self-explaining that there is nothing else you can do.
"The core happening in the informational domain through digital platforms, which will soon migrate to synthetic virtual spaces." - wow, that sentence is packed! What is a "synthetic virtual space"?
Buying from local vendors doesn't have to do anything with politics. From groceries to software it makes perfect sense to me to buying locally. The money i spend in my town or country will have much bigger effect here again than when i spend it in a different country or even a continent
I have a T430s which was handed down to me by my boss 10 years ago. It has i5 from that time, 8Gb RAM. I'm still doing web app development on it same as 10 years ago and i don't feel any need to change it. I'm actually afraid there is no better laptop i could change it for when mine dies. Also i can't imagine no better keyboard :(
This is so true. I wish MacBook didn’t have such shallow keyboards or I’d be all in. Maybe it’s improved recently but at one point it was like typing on a table. Always loved the travel of the ThinkPad keyboards.
ThinkPad keyboards also got worse (flatter) every couple of generations, sadly. My laptop with the best keyboard is an R50e from 2004. The keyboards are still nice compared to most current ones, but...
The T420 keyboard is far better than the chicklet T430s. It’s a proper mechanical keyboard.
I’ve got both, have used both for webdev work, but compared to a modern laptop, the screens suck, the video is underpowered for 4k monitors, and the ssd interface is slow, and the trackpads are awful. On the bright side, trackpoints. (But I’m using a M13 w/ trackpoint so…. ) They’re also heavy and battery life is almost long enough to work the whole way on my bus commute, one way.
I have a T420 I've been using for years. Upgraded to 16GB of RAM, SSD, swapped the dual core i5 for a 4 core/8 thread i7 (yes, the CPU is in a socket!), and swapped the 1600x900 crappy display for a newer 1080p panel that looks much better. I absolutely love this laptop and am not looking forward to the day when it's too old for the modern web.
I have a T440p with 16 GB of RAM and a T480 with 40 GB of RAM (that can be extended again to 64 GB) and I'm also pretty happy with both and worried about the future of computing. I might stockpile a few of them!
I upgraded from 8 GB to 8+32 GB and will upgrade to 32+32 GB when the need arise but so far I can do web dev with that (16 GB is definitely not enough anymore sadly).
Same, T460 and a T480 I think. Updated to an SSD and maxed out RAM. My only quibble is max 1980x??? Screen resolution. ThinkPad are so cheap when they come back from their leasing contract, not sure why not more people are excited about them.
Even if you don't use Linux, they typically come with a Windows Pro license built in.
You can upgrade the screen too, at least on the t480
For around 100$ and some manual work you can upgrade to 2k resolution with say a B140QAN02.0 screen or heck even 4k if you dont mind spending twice the laptop's worth on that
Absolutely love that laptop, tricked out mine with 64gb of ram (absolutely overkill but hey I could) and a X1E glass trackpad and it's been my main dev laptop for the last 5-6 years
A 6e wifi upgrade is somewhere on the roadmap as well for me
I also pay for Kagi and i'v never been happier with my searches. It's so nice not to have to slog through Google bullshit results. Kagi results are great and you can tweak the behaviour deeply to your liking. I'm also proud to support an alternative from a smaller company with same beliefs instead of Google who does a lot of damage to the medium i love be it ads or Chrome. So the few bucks are a no brainer. It's the same as paying for any other monthly subscription
The event yielded a few commits to the Ruby CNB, but none to any other deploy or build tools.
I left my session open ended and that resulted in a fix to a surprisingly difficult to debug problem in syntax suggest (runtime syntax parsing error tool I maintain). Thanks to Andy for pairing with me on it over the session https://github.com/ruby/syntax_suggest/pull/232.
Overall the in-person hackday was long, but fun and rewarding.
Because it gives money to people I don’t want to have that money, even if I turn off any features related to the people that I don’t want to have money.
I've been using it for a while now. It is marginally better, but not exactly night and day. It seems to struggle with intent at times, and others I just get the same bland results as the free engines. The privacy is a big plus however.
Probably because it costs money and it also likely also will quickly succumb to sloppification by experimenting with their own ai and having an unstable founder…
I'm using it for about two years and i haven't seen any sloppification. I see it as a feature that it is a paid service because i hope it will be a sustainable model for them to keep it as it is. I think it's a no brainer to pay for it instead of all the suffering people describe here. The founder remark i don't get
Right now Kagi is a better search engine than Google. Why should some eventual demise in the future discourage anyone? There is no cost of switching and you can start using it right away
Would recommend to just try their 100 free searches.
Their results are good, but it’s hard to have an objective measure. For me, it’s the little features that make it worth it (and that they have a forum for feature requests, and a proper changelog).
I've been disappointed with pretty much all recent SEs (DDG being among the very worst). Having been an early Scroogle user, ixquick (startpage) and a few other ones I dearly miss, I've been using https://freespoke.com/ lately and find it tolerable.
I was using searx instances with reasonable results but many of them started failing recently.
Anyway, I hope everyone finds a good one. I fear things will only get worse though.
There's no rush to move away from MailCatcher or MailHog, but if you're not using those solutions already I see no reason to use them over the maintained options.
> I see no reason to use them over the maintained options
Things that don't change over a longer time period can be more comfortable sometimes. Especially things you use often and build up a sort of "muscle memory" about.
Yeah, people underestimate the value of “finished” software: in an ecosystem with lots of stable dependencies, there’s very little reason for useful software to change constantly.
Even "finished" software needs maintenance. Nothing is ever bug-free so needs fixes. And it doesn't live in a vacuum, the ecosystem evolves and continuous adjustments are needed when APIs evolve or libraries change.
In well-written software, the maintenance burden is low, but it's not zero. Without any maintenance, you can maybe run some piece of software in some closed-off container for a while, but it will keep rotting away and eventually you won't even be able to compile it anymore.
What about "GNU Hello", never finished? Clearly this isn't true for 100% of all software, so the only thing we can conclude is that it either "depends" and/or is very subjective.
> when APIs evolve or libraries change.
If you live/work inside an ecosystem that favor stability over "evolving APIs", you can actually be able to use libraries that are decades old, that doesn't have any bugs for the stuff they expose and things just work. I mostly experience this in the Clojure ecosystem, but I'm sure it's true for other ecosystems too.
Does "small burst of activity and dependency updates twice a year" seem inadequate to you? That's the scale of maintenance that the project in question seems to exhibit, which is what we're apparently calling not maintained.
Commenter was just making the fair point that the dependencies are out of date.
Maintenance doesn't always mean UI redesigns or non-compatible config changes. Sometimes it is just fixing bugs and updating or replacing old dependencies.
It is complex but not complicated. You can start with just a few small parts and get to a usable and clean document within hours from the first contact with the languages. The tags and rules are usually quite self-describing while consice and there are tons and tons of good docs and tools. The development of the standards is also open and you can peek there if you want to understand decisions and rationals.