There are proposals with some traction that would enable webbrowsers to parse TS, but simply ignore the types.
I think it's a bad idea, because tooling handles that perfectly well and I think browsers should generally avoid building functionality that could be equally well provided outside it, but I guess enough people have been asking for it, so it might happen.
I think it's totally fair, but I would assume that most Spring projects make significant DX tradeoffs compared to a full JS stack or serve an API rather than html.
1. Spring + Handlebars: You can either write the html template in a string loosing syntax highlighting and other LSP stuff, load it from a file loosing colocation.
2. Handlebars + webcomponents. They simply bundle all the web components into a single file, which breaks down when they get large and you don't need every component on every route.
3. Tailwind: Looking online you can get it working with spring boot, but the route chosen here is a script to run the cli, which again means every route ships every tailwind class used anywhere.
The article lists, things like transpilers, polyfills, tree shaking, minification, CSS transformation, then declares that this is all super complex and that we need to start over.
To me as a dev these are elements that have started to work transparently a long time ago. It just isn't something I worry about in my day to day frontend work, the same way a Spring + HTMX user doesn't care about the Java -> JVM -> Assembly pipeline.
The most complex things I deal with as a frontend dev is
1. Browser issues
2. Server client communication.
Part of what makes a good user experience is is working nicely with the users hardware and software stack and that's much easier on the client.
The user would like the website to have native scroll physics, respect their system preferences, react to changing window sizes and with different input methods, screen readers and so on.
If the key to a good user experience was server side control, than the hallmark of a good website would be being an RDP stream and prefers-color-scheme wouldn't be a CSS feature but a HTTP header.
Yes, but it's not the fault of these frameworks.
If people wanted to they could ship source maps on purpose and not just accidentally.
Not exposing source code was one of the early drivers for tooling.
I think it's fair to say there are plenty of people in Apple's leadership that would have had the authority to tell Alan Dye "no".
They didn't. I think it's fair to say that the company leadership likes liquid glass.
The reaction to it was about as divided when they presented it as it is now. If they thought the backlash warranted a change in direction they could have pulled it before it ever made it to users in the fall, like they did with numerous attempts at shipping AI features.
A major reversal in the next version would make a lot of people look really really bad.
The missteps of those intel MacBooks are undeniable, but I also feel like the new design feels very safe and unambitious.
There is the huge notch.
The 16" model is (given screen and battery size) 35% heavier than competitors and not exactly a joy to lug around.
The keycaps continue to be made of subpar ABS getting a oily look within mere month of usage.
The use of space inside is not very efficient compared to previous models.
Cursor seems to be pivoting to a Codex like desktop app.
The real product though is probably their decently tuned harness and their composer models.
I agree that their popularity has waned. I would attribute that mostly to customers chasing the most subsidized tokens and Cursor not having the pockets to keep up. Anthropic is already following suit and it seems unclear how long OpenAI is willing to continue. I think in a case of a market correction that forces model makers to adopt more reasonable growth targets, that Cursor is decently positioned.
I really doubt they'll swap in Grok. Grok seems pretty dead. Probably more likely they'll reuse the hardware for composer.
If value is a concern, Codex. It's pretty hard to beat those subsidies. If you really want model freedom, Copilot is surprisingly decent value and as of right now let's you use your sub in other harnesses like OpenCode.
I think composer has currently by far the best price to performance ratio for coding (not counting subsidized subscription cost by OpenAI and Anthropic).
It's based on Kimi K2, but I think it's fair to say, that their RL really sets it apart from the other open weight models.
I do think the Codex harness is a bit better than others.
Doesn't make a ton of difference with OpenAI models, but with Google and Anthropic models the difference is quite noticeable I think.
Even if it wasn't for Musk, are these relationships really worth so much?
There is a certain value in being on the approved vendor list, but it seems to me that there really isn't a lot of vendor lock-in.
I think most people could switch to opencode, claude code or codex pretty easily.
Maybe these relationships would be worth a lot if companies signed long-term contracts, but I doubt many did.
In a per capita sense of course.
But it does pose an interesting question. To what degree does the quality of rail scale with absolute investments vs per capita investments.
On the face of it rail is almost entirely fixed cost.
The capital investment for tracks, trains and the operating cost for staff and energy are fixed to matter how many or few people the trains are serving.
The crux is that for a given cost the quality scales inversely with the population and covered area.
Transplant the Swiss rail expenses to Japan and it would make for a pitiful experience. Stretching over an area 9x larger and having to serve 12x more people, simply requires a lot more rolling stock, track and personell to offer a similar level of experience.
In particular when talking about rural rail service it's most apt to compare areas of similar size and population and in this local sense Switzerland is not just richer per capita but absolutely.
I don' really understand where people's enthusiasm for the hardware comes from (aside from the chips).
They have corrected many of the functional compromises of the Ive era, but it seems otherwise unambitous.
The recent Pro iPhones have a certain unflattering chunkiness.
MacBooks have also grown to an uncomfortable weight and lost some of the elegance of prior design.
They also suffer from an unnecessarily huge notch.
On top of that there are a number of products whose usability concerns never got addressed. AirPods Max and Vision Pro are too heavy to wear for a long time and the ergonomic travesty of using and ridiculousness of charging the Magic Mouse remain unaddressed. Apple Watches got a tenth of the standby time of Garmin and other sport watches.
It's not that the hardware is horrible, but I think if it weren't for the ecosystem and chips most Apple products would seem quite unremarkable.
I know that for myself exercise increases my resting heart rate in the short term. It only decreases after a day or two, sometimes more depending on how fatigued I am.
I thought that was common, with recovery times obviously decreasing the fitter ones gets.
I think it's more politics and economics.
Switzerland is quite a lot richer than Japan and is extremely decentralized politically.
That creates strong incentives to provide good public services even to mountain villages.
It also helps that Switzerland isn't experiencing population decline. The Swiss population as a whole is growing quite rapidly and from what limited data I could find even rural regions are growing.
I think land acquisition doesn't really play a huge role.
They are both mountainous countries where rail projects have to squeeze in valleys or bear the expense of tunnelling.
I'm bloody sick of it, but more exhausted than bored.
My workflow that was pretty stable for years, keeps changing massively on an almost monthly basis and that means I'm already skipping the fads of the week.
What's more annoying is that it feels actually worth it and thus keeps me churning.
The vast majority of DRM protected content (or at least majority by watch time) available in UHD via torrent in a matter of hours.
People like to stay away from torrents, because it carries significant risk in many jurisdictions.
But the only reason UHD versions are only available via torrent and often not as streams or downloads is bandwidth cost.
I can't see how it has any thing todo with DRM.
The only thing it maybe cut's down is sharing within friend groups. But even then it only takes one to figure out how to set up a VPN for torrenting.
yes it would, but depending on the app it could put you in a ton of hurt.
- AI has gotten a lot better on less popular tech, but there is still a big capability gap between native frameworks an the blessed react + tailwind stack.
- You will get something that is likely in the right shape but littered with a million subtle bugs and fixing them without having intimate knowledge of the plat form is really hard.
This might be a "the grass is greener on the other side" situation because I do a lot more web than native dev, but in my experience native while just as quirky as web will usually give you low level APIs to work around design flaws.
On web it too often feels like you can either accept a slightly janky result or throw everything away and use canvas or webgl.
Here are some recent examples I stumbled across:
- try putting a semi transparent element on part of an image with rounded corners and you will observe unfixable anti-alias issues in those corners
- try animating together an input with the on screen keyboard
- try doing a JS driven animation in a real app (never the main thread feels hopeless and houdini animation worklets never materialized)
I don't think it's that native has nothing to offer. I think that developing (in case of desktop) for 3 different platforms all with own complication of what is native UI is a nightmare. macos has swiftui (incomplete), uikit and appkit, linux in practice gtk/qt, windows winui 3 (fundamentally broken) with WPF and WinForms still hanging around .
I can see it going both ways.
If knowledge work continues to roughly look the way it looks then I think maintenance is going to be an issue. Both in terms of keeping the spaghetti together but also in terms of all the bad design decisions you get from everyone bolting on their ideas.
If however knowledge work becomes just talking to LLMs and occasionally interacting with an on the fly generated UI then maintenance becomes a non issue