skysight-inc/HackerNews huggingface dataset:
Your second paragraph disproves your first. Websites' needs didn't drastically increase (I'm ignoring nonsense like WebGPU; render graphics outside the web browser like a God-fearing Christian!), but their complexity did. Why? Well, we told everyone with a pulse they could make six figures "doing web development", and we're reaping what we've sown.

You can still design websites like it's 2005, and they'll be damn fast. But pitch something like MFC or even PHP to a 20-something frontend developer now and watch the blood drain from their face.
> I thought in general it was widely agreed upon at this point WFH is at-least a 10% drop in productivity. Stanford has been doing plenty of research in this area. The argument in favor of WFH has for the most part moved on to now cost savings from not having offices lets you hire more people to make up for the loss in productivity.

I wonder if they covered that people working from home may get sick less and work longer hours.

Ye gods, I can concentrate better at home than I can in an open floorplan office lol :D
Dragon Arm(tm)?
I don't know how to thank you for this great gift you are giving to all those who like me want to learn German. I'll see it and let you know. For now, thanks
Absolutely.

Using a recommendation algorithm similar to TikTok’s, learn what each specific user are into, and instead of showing content produced by other users, produce custom-tailored content on the fly, perfectly matching the type, tone, style, length, and rhythm each user likes.

Ideally without making anything up.
Hitchhiker’s Guide to the Galaxy Text Adventure
Here's a good explanation of what they are doing https://www.youtube.com/watch?v=tpbbschYKjE
It's also a straightforward implication of relativity. If there was offset like that between a mass and the point that gets orbited, then you could measure the objective speed of the mass relative to the aether.
The author writes >> I’ve seen numbers written inside of a <li> that’s inside of a <ul> — instead of just using an <ol>

An ordered list <ol> automatically adds a number to each list item indicating its position in the order in the list which would save developers the effort of adding code to insert numbers into ordinary list items in an unordered list.
We gained a vision around correcting the supply shocks that occurred in the early 2020s. The price of many goods went sky high due to lack of supply, so people started demanding money again so that they could ramp up production in response. Thus the price of money (i.e. interest rates) increased on that newfound demand.

You are right that it is probably not a suitable long-term vision. In fact, it seems most everyone is convinced that interest rates are going to head back towards ZIRP again soon because they don't see any long-term vision out there to sustain that demand. You are good company here.
Try this:

https://a.aliexpress.com/_EyK6Rjh

I use them in phones, laptops, Flipper Zero, anything which takes USB C.
I have a list of learning resources for CLI tools and shell scripting here: https://learnbyexample.github.io/curated_resources/linux_cli...
There are lots of open source consultancies (Igalia for example does a lot of work on web browser and lower layers), and some projects have lists of available consultants:

https://github.com/fossjobs/fossjobs/wiki/Resources#freelanc...
> That's because we subsidize the world by investing in a massive portion of the science and tech for producing medicines.

Even if we assume that's the case - as in, normal margins would be insufficient to finance the research - that does not account for the medical treatments themselves.

> the whole world laughs at us

Most of the world doesn't care.
> Does the US actually fall behind other nations in health outcomes?

For the world's richest people you couldn't do better than to be a patient in America. For most Americans though, the US healthcare system is failing them. America does worse compared to other nations in some very basic measures like having a lower average life expectancy, a higher infant morality rate, more obesity and congestive heart failure and more hospital/pharmacy screw ups. A child or teenager in the US is less likely to live to adulthood compared to those in other developed countries. It's not any better when it comes to mental health either. The US is one of the worst nations when it comes to mental health outcomes and suicide and drug related deaths are higher in the US. Over thirty percent of the US population has been forced to put off getting the care they need due to the cost and preventative care is usually the first thing that people cut back on leading to bigger problems that could have been avoided entirely.
The Story of Life
It sounds like your issue is with the syntax of Jinja, and the hellscape of HTML email. I'm not sure how 20 MB of inscrutable JavaScript would help, considering it's also just template rendering with extra steps (bonus: using the user's CPU cycles and power instead of your own).
You're so caught up in your polarized hot take that you completely ignore why people don't want to live in empty areas. A lot of people don't want to live where it's empty. It's really that simple.

They like being near other people, having access to the services, don't want to waste precious hours commuting, and that's where the jobs are.
I had been programming for about 30 years, I loved it and was excited by it. After work I would go home and work on side projects.

React single-handily killed it. It encouraged, usually required, all of the awful design patterns I used to chase all the junior engineers and interns about. This has become endemic in the JS world.

Here's an example: did you know that the uuid npm used Math.random up through 2020 (v.7)? Cryptographically secure random number generation had been available in basically all browsers since 2011. 9 years. If I had an engineer submit that code, I'd rake them over the coals.

Speaking of that, I'd usually need a half-time engineer on larger projects just for the management of the complexity. All of the various frameworks and updates and breaking changes. It was a 20/hour a week job just to stay on top of things. For instance, koajs.

It's a bunch of dependency code of quality I would never let fly, but now I have to use it and grow my team, increase budget, push back deadlines - all to manage the piles. No thanks.

I left that job, quit the industry entirely about 2 1/2 years ago. Reactjs was such atrocious self-aggrandizing bullshit, it made me quit programming. It's fragile, over-engineered, mostly broken, confused poorly defined amorphous concepts that poorly solve mostly imagined problems and the entire industry of front-end is eating up that mode of design like it's some sacred text.

They'll use abstract buzzword concepts that have different conflicting definitions in basically every text you pick up, and they'll never concretely define them but continue to use them as abstract amorphous blobs.

I've got very popular front-end projects. I've been at the C-level of more than one company that sold based on front-end design. The first professional javascript based web app I did was in 1997. I deployed Server Side JavaScript (SSJS)/LiveWire in the 90s, a decade before Node ever existed. I've been at this for a long, long time.

After dealing with react, I never want to touch that stuff again.
Personally as an English/Japanese bilingual speaker and a programmer (programming languages!), I think the most important thing is incentive.

Why do you want or need to learn that language? Is it important? Is it valuable? Is it fulfilling?

As I've found, the biggest "wall" to learning languages is convincing yourself that learning the language is worth the immense hassle and effort.
a few days ago when kremlin asked mozilla to remove anti-circumvention tools from mozilla store, the internet exploded with "sold outs" and "succumbed to pressure of the oppressive government" but now here we are.

isn't this hypocrisy? on your part, i mean the HN crowd
> I've been reading and writing HTML since the 90s and off the top of my head can't recall ever seeing <ol>

I have to ask: is this /s? Are you really saying you never seen an ordered list in 30 years working on the web? How about <dl> ?

If you’re not joking then it’s honestly wild to me.
> Gaming on OSX is a disaster due to no official Vulkan support and OpenGL capped at 4.1

Game development on OSX is fantastic for thousands of iOS game developers. iPad games can often run out of the box.
Doing something the right way is:

(a) less work

(b) scales from 10 items to 1,000 to 1,000,000 items effortlessly

(c) works the same no matter what number system you have localised, such as greek, chinese, icelandic and arabic.

As in any profession: use the right tools for the job, otherwise you're bashing in a nail with a screwdriver and scorning the guy using a hammer.
> jinja

As a home assistant user, jinja in yaml files is hot steaming ass.

Every time I read the jinja manual I want to cry. And a small part of me dies in side. It's like a templating language designed to get even with the person who microwave a tuna fish sandwich in the office, for lunch, daily... That some how leaked out to the web.
Remember, it's not the language. You can write COBOL in any language.

I want to see good techniques, testing, and practices in any code that touches my money. I don't care what language they write it in.
Right. I think it's probably Spotify or equivalent somehow nudging them onto playlists of cover versions that are cheaper for them rather than the shops and restaurants explicitly making the choice. But it's a trend I've noticed that I thought was interesting, and suggests that cost is having an effect at some point in the chain.
Except that because they are "free", they drive out any semblance of competition which would serve as a check on the super shitty customer service.

As an alternative solution, I'm all for splitting up Meta, Google, etc for being anti-competitive.

If Gmail, YouTube, Facebook, Instagram, Hotmail, etc. all had to stand on their own without being able to share revenue from other sections of the company, the "free to prevent competition" would go into the trash can where it belongs.
I was wrong in my guesses.

More information is available here: https://www.theregister.com/2024/06/20/musk_dell_supermicro_...

Dell and SuperMicro are building this for X.
> This did not happen in music.

Copyright thuggery is the reason why
I think that's the point. Supplementing up to a given minimum has counterintuitive incentives, causing the program to pay more in aggregate than if it had looser caps (and linear scaling) and let more people work and earn slightly higher incomes by reaping the benefits of the program.
The sample they used for training are mixed.

Unless they can have enough raw, unmixed sample, this depends on how well they "unmix" them.
Hard disagree on that personally. But I guess it depends what industry you’re in.

Life’s too short is a cop-out especially because it doesn’t take longer to use a semantic tag rather than a div.

With “life’s too short” you can justify pretty much everything.
> I personally do all my sites with 100% server site rendering and bits of JS here and there if I need some interactivity that can’t be done with CSS alone.

So actually not "100% server side rendering" at all. And probably paying all the costs of using JS more extensively, but gaining fewer of the benefits.
I can speak German, English and Dutch (which are very close Germanic languages) and also understand a bit of French and Italian. I guess I could learn their basics relatively quickly if I tried hard enough.

However, I actually need to learn Croatian, a Slavic language. This is extremely difficult for me and I make hardly any progress. The vocabulary is so different from everything else I know, I just can't remember the words. The grammar is quite challenging as well.
The Paradox of Learning to Reason from Data (2022)
For comparison, in the native world program is considered vulnerable when someone finds arbitrary write primitive (even without leak), use after free, and even double free. There is a huge gap between these and actually having a working RCE exploit. Most CVEs in this space are given without a working exploit ever written.
Fry's Electronics (this was long before they shut down)
What's your sales experience? If the answer is "none", then you'll discover that bootstrapping is not nice at all.

---

1. Services business, had a few clients that I knew would say yes.
2. None. But trying to pivot away from services to products -- dozens, none successful.
3. When you have a good pipeline of clients, it's great. Then it can all come crashing down to zero in a matter of weeks.
4. I want to, but now I'm essentially unemployable.
5. Solo.
6. Found myself back in academia of all places, and simultaneously advising large corporates on how to make use of language models.
Windows have really evolved and improved as an OS. WSL2 + vscode is almost replacing my need for a VM or a linux box for most of my needs. The oss is also much more stable, the update less annoying and the UI/design language pretty nice.

Sadly MSFT being MSFT, after all of this progress, they are now regressing with ads and news inserted inside the desktop. Weird telemetry and loging requirements and now with AI everywhere.

And if any one from the windows team is reading this... FIX DESKTOP SEARCH :)
> another prime example on why borders are stupid

Might want to start with the free movement of people before you go abolishing borders of all kinds.
~~No.~~ Yes, but you should also ... . To maximize the impact they can have.
A TOC is a nested ordered list. You can make that today by nesting <ol>.
SPA shouldn't be used for content heavy web pages anyway. SPAs today especially React were basically like Facebook's engineers decided to write js/css/html in the style of php.
What a silly rant. There is a huge world of different approaches to front-end and lots of them do cool and interesting things that would both up your productivity and give you completely new opportunities ... if you bothered instead of just being an old fart.
Tend to agree. The “piledrive” article yesterday was the same. It’s not that the author didn’t have good points, and it’s not that I even mind profanity. I just think the shocking language is a stand-in for a stronger argument.
Conways law:

React is a Face Book abstraction leaking out on to the web.

It's good for them. It's a perfect framework (+ graphQL) for there every page is custom in a walled garden environment.

It isnt a good way to build a blog, or a shopping cart. But A mail client in a browser, or a B2B app with a lot of data, A CMS... great places for it!

And it's great for FB too. (as is every other open source tech from a large player). Think about all the money FB saves NOT having to ramp up front end engineers... they get them pre-trained now on their tool.
gaming != game devolvement though...
> It's an argument which you could extent to any pathogen: why would any disease kill its host?

Moreover, why would a disease even 'care' about the host? As long as it can jump hosts quickly, it can afford to kill many of them. If achieving fast transmission is tough on the host, so be it. Other diseases may select for the opposite approach, of course.
If an organization made a deliberate choice of not paying 5000 USD/mo for extra security, then security is less important for them than this amount of money — so they get what they pay for, and it’s their responsibility.
I think that, most of the time people think they've seen such marketing material, the intended message was really "we're primarily interested in doing business with huge needy clients". For some kinds of software it's fundamentally hard to reliably make money from small users.
Semantic HTML elements and the semantic web are not the same thing. The semantic web was about linked data and RDF and suchlike.
Salesforce purchasing is the same. As is marketing automation platforms and BI tools. And confluence/jira. People buy what they already know.
Execute Commands by Sending JSON?
i cant count the number of times i've had to generate boilerplate + interfaces etc etc for something that would be as simple as an onclick (onClick?) handler would have done. i have yet to actualize the serious promises of this ecosystem in any meaningful way and it doesn't seem to get better. also jsx is ugly.
>Get ready to pick up a ton of cheap hardware in a year or two…

Why? As far as I know, we're hugely bottlenecked by hardware in both training and inference even for current models.
There's nobody more confident in the world, than HN poster wiring about a topic they have no experience with.

There is a huge gap (in the binary exploitation world) between identifying a problematic code pattern and having a workable bug (a reproduction), and even larger one between a reproducible crash and a working exploit (because we're not in the 90s anymore and complier/hardware mitigations are literally always enabled). Current LLMs can cross neither gap, and are not even close to bridging the second one.
Could it be that you never tried to understand react and why the approach makes sense to millions of developers?
Cost vs. benefit. If the ARIA roles are all in order (which can admittedly be a pretty big "if"), there's no user-facing benefit to semantic HTML over arbitrary HTML with the same style.
> I often think back to Fauci during HIV/AIDS while reflecting on the current situation around COVID and I think we got lucky to find somebody like him, even if he said a few dumb things, and we'll be lucky if any public servants are willing to take up his role in the future.

Hopefully, the next administration doesn't come up with Schedule F once again and make all health-related government jobs political.

https://en.wikipedia.org/wiki/Schedule_F_appointment
I found it weird as well to see that. I didn't know LangChain overrode Python syntax.

But, if you're familiar with Linux/Unix, this should be familiar. You are piping the output of one function as the input of another function.
I fear that so much about what the web is has been forgotten. I've had some surreal discussions with frontend devs that don't have a fully formed concept of what a URL is. Their solution to "sharing" is to either have their users instruct each other using words on how to find a particular page, or to propose some overengineered URL shortening scheme to encapsulate state which belongs on the path or query string. It really feels as though usability is being treated as an afterthought.
Screen readers and other assistive technology fully expects your HTML to be semantic. It doesn’t always matter, but it matters often enough.

CSS tends to be hard because (1) people insists on having a single page with a single stylesheet and (2) only divs are used, and so they use class names for everything.

If you didn’t use a SPA you’d have scoping. If you used semantic HTML you could target based on semantic structure. Both of these makes CSS easier.

JavaScript is fine to use if you have to. But using JavaScript when you don’t is just wasting time. I’ve seen people essentially re-implement default <form> behaviour too many times to count, and spend time looking for solutions to problems they only have because they insist on using technology for making interactive sites when they’re making something largely static.

If you want a simpler life, choose the simplest technology that will solve your problem.
And then wrap that in a <nav> element.
There are different template engines for SSR, with drastically different syntax. I've never written any Python, but in my own opinion, Smarty for PHP and Twig-compatible ones for many different languages are the best.

While generating any moderately complex HTML on the front end is a pain in the ass for me. I prefer avoiding it. If I need to request some data from the server to dynamically update the page with, I just make that endpoint return some server-side-rendered HTML that I insert wherever it needs to go.
For the most part yes, the deno plugin relies on the deno language server though.
This echoes our experience with LangChain, although we have abandoned it before putting it into production. We found out that for simple use cases it's too complex (as mentioned in the blog), and for complex use cases it's too difficult to adapt. We were not able to identify what is the sweet spot when it is worth it to use it. We felt like we can easily code ourselves most of its functionality very quickly and in a way that fits our requirements.
Source with more information: https://www.tuxedocomputers.com/en/TUXEDO-on-ARM-is-coming.t...
Debian is where I went to get rid of snaps. My Debian 11 desktop is indistinguishable from my old Ubuntu 22.04 one and my machines feels a little faster. It didn't spin the fan much with Ubuntu, it spins it less often with Debian.
What the hell are you even taking about?
Is anyone else not seeing this in their console. I still only see the old sonnet.
It is basic Markdown... maybe they never investigated the HTML Markdown produces on GitHub and so on? <ol> does seem hard to avoid.
Being interrupted is a pain because it can derail your train of thought. But I think many people interrupt in order to avoid derailing their own train of thought by waiting and/or writing something down, or simply because nobody else will stop talking or pay attention to them.

I've also observed "full duplex" conversations where people overlap periodically but don't seem to have any trouble continuing. And I've been in meetings and zoom calls where you can't get a word in edgewise until the meeting is over.

I've tried to become more tolerant of people who seem to be interrupting to express something important in context.
We don't build websites anymore, we build web apps

It make seem trite but you just aren't going to have a good time building some of the stuff people build now using a LAMP stack
Picard and Dathon… at El-Adrel
> Ubuntu with its Unity design first, then Snap, put desktop Linux back a decade. What a way to snatch defeat from the jaws of victory. A SUV.

Strongly disagree. It seems to me that Ubuntu was( and still is) the main driver behind most of the improvements in the linux desktop space. The linux desktop experiences lagged being MacOS and windows for years. Even after ubuntu transitioned back to gnome, they still made a lot of improvements which lead to significantly better UX.

The curse of linux desktop, is that the linux community seems to be allergic to any changes be it systemd,unity or snap packages.
> I used to write front end applications with MFC (Microsoft Foundation Classes, which is C++) using Visual Studio circa 2005, and it was never as complex as an SPA today. There is something wrong somewhere, and I don't think it's JavaScript or the DOM.

No, it's CSS. No real UI framework has anything remotely like CSS, and for good reason. But people like the author of this article keep trying to make CSS work instead of writing it off as the mistake it is, and so web development remains awful.
Frog pond are loud.
I personally do all my sites with a close to 100% client side rendering as I can get with modern JS frameworks. If I wanted to SSR I’d use PHP…
Yawn, another case of “new is bad because I don’t understand it.” Being nostalgic for jQuery? Really?
What? How could you have been writing HTML since the 90s and not see all those examples of OLs with numbered items, including lowercase roman numerals or uppercase letters?

Somehow, even if I never used roman numerals, that example sticks in my head (esp the lowercase).

Anyway, if you cared deeply about content in the 90s, you might have focused on the semantic meaning behind tags (I've also looked a lot at other SGML and later XML based formats like TEI, DocBook...), tried to strictly decouple presentation (CSS) from the HTML (content), and be annoyed that the CSS box model never supported nice content-related flow features like TeX did since the 80s (and still doesn't).

Now, don't get me wrong, I wasn't some wizard — I was simply an easily impressed (with things having some meaning) high-schooler around that time :)