Relax for a second. Get some perspective.
2,301 karma · joined June 28, 2012
Relax for a second. Get some perspective.
That's the wrong way to look at it. NeoVIM has a different concept of care for their users. They're optimizing for another kind of care, more in line with modern expectations, which VIM did not care about (hence the fork).
It's not better or worse, just different.
This same article could've been written about how VIM has no native LSP integration or autocomplete and they don't have duty or care for their users.
Other languages and their implementations of green threads usually have cooperative scheduling or M:1 mapping
If they wanted to be a more independent country with an independent economy they'd need to revise some of their policies.
Most of China development is sui generis and not replicable elsewhere.
You don't have to be exclusively one race to be a unique country. The US just hasn't achieved a blended culture, but it doesn't mean it's not possible.
That's almost a uniquely United States problem, not at all as big of an issue in most of the Americas. Only a few countries in the Americas have had their native population pretty much entirely wiped out without any assimilation whatsoever. The US is one of these few countries (Cuba and Hispaniola would be other examples of total replacement).
The rest has had large degree of intermixing or wholesale population preservation. Aspects of native culture is those countries were suppressed historically but are still preserved in some way to this day.
It's also very fair to say sovereign countries today can build a healthier immigration policy than 1500s Europeans with their extermination campaigns. I'd be the last to say that is an example to be followed.
More to the point here: Japan can be exclusively Japanese for another 200 years and die forever, or be Japanese + something for another 10 thousand years. Unlike 500 years ago, they get a choice.
Ultimately it’s their choice.
Whether a country with high population composed of immigration is still the same country we can look to the Americas. Countries with extreme high degree of immigration and assimilation, yet still very much worthwhile countries. Maybe not the countries the natives from 500 years ago would have imagined, but their culture has survived more than 100 years and contribute significantly to the world still. New Zealand is also a good example of native culture not being wiped out even with assimilation.
And the unemployed youth would be working those low skilled jobs today if they wanted to, fact is they don’t pay enough for them and if those jobs are automated away they will still be unemployed.
It obviously suppress wages, which is a necessary condition for capitalism. Any country where it costs 10x to build infrastructure because there is no cheap labor will be less competitive.
Foreign labor is what will keep most of these countries afloat for the following 50 years.
Japan is a good example, they lose about 1 million every year.
Plus indoor spaces never get that hot due to shade and passive cooling. A little breeze and 90 F is just fine.
Yeah. It's very weird/funny hearing how 100 F is almost death to them, when it's really not that bad. Most people where I'm from are practicing sports at 100 F.
We have child-free hotels, child-free restaurantes, maybe now child-free airplanes...what's next, child-free cities?
Some other countries might still develop ideas but when it's time to actually put it into practice and scale it seems it'll always require the Chinese to play a huge part in it. They're the only ones with appetite for "unprofitable" projects that have returns in decades.
The US population is much more pessimistic and doomsday driven these days, whereas the Chinese are more optimistic and future driven.
Just like this has made Web devs into Mobile devs, so could Mobile devs leverage AI to work in Web shops.
I'm not an optimist but there could be an increase of available apps being created which would still keep people employed. Theoretically the cost of creating an iOS app for a company without an engineering team dropped from several hundreds of thousand to a few thousand or hundreds, which could be paid out to a freelancer with AI. More people would go into freelancing for industries which were not contemplated before due to cost.
But I'm not an optimist.
If one wants to do server side rendering with HTML templates like the old days there is no real “components” way of doing it (although declarative Shadow DOM is coming along). Partials are not the same thing.
In that scenario some repetition can give you the benefit of keeping a clean stack with no client side rendering.
I have never seen a single website where performance downgrade was caused by HTML.
However I’m not advocating for it, just making the case that it’s very hard to do worse than we’re currently doing with front end development.
Yep. ADAS should be mandatory like seat belts and airbags. A regulatory body should be able to come up with a minimum standard for it.
Full self-driving doesn't strike me as necessary to prevent deaths.
They can now.
https://www.checklyhq.com/blog/agentic-rewrite-nodejs-to-go/
They had a very good run for such a project.
[1] - https://adamwathan.me/tailwindcss-from-side-project-byproduc...
I'm not a huge AI person but it's obvious a host of great tools we've built to deal with our challenges would not have been significant if we had LLMs.
A very crude example: to translate code into a different language someone would need to write a tokenizer, a parser, an AST and finally a translator. All significant engineering challenges, taking days to finish. Nowadays you can tell an LLM to do that in minutes.
Staying on topic: we could easily argue that CSS wouldn't have existed if LLMs existed and could create table layouts from pasted images in a chat window.
A major point of components is having a single place where you can change design and behavior across your entire codebase. With LLMs you can with very good accuracy tell them to change the look of "all buttons that are confirmation buttons in modals but not in the login modal". Doesn't matter if there are 10 such buttons or 1000, it'll take a few seconds for them to accomplish it.
I'm slowly forming the opinion that nowadays having copy-and-pasted "components", with their whole HTML just repeated over and over, is now a much less worrying thing in a codebase. Even a bloated CSS can be quickly fixed by a LLM.
And like you said: you eliminate the build phase entirely and frontend development ergonomics goes back to how it was in the early 2000s.
Tailwind's business model existed due to a massive inefficiency in the frontend industry not being able to come to terms with CSS or native components. They surfed the wave of JS frontends becoming ever more complicated. If it wasn't AI and just a human awakening to that fact, realizing that the complexity of modern frontends and Tailwind are not an absolute necessity, they'd have lost business just the same. There are dozens of different ways of writing frontends that have nothing to do with Tailwind.
Providing ready-made UI components and templates has never been a million-dollar business, nor should it be.