Eh, most of the benefits are offset by the stress of having to care about the needs of corporate america and all the ensuing implications of making a living by destroying society. Just because it's not a physical job doesn't mean this stress won't kill you.
It's also worth noting that developers remain some of the most proportionately under-compensated jobs compared to the revenue we drive and we're all aware of it. It's the shareholders that need to justify their existence.
I suspect many of these open source developers are employed in this capacity on some level by for-profit corporations (which sadly does bring a high degree of dysfunction in terms of resource allocation). But I can't imagine being this productive as a side-gig.
Not really. And "finding one's voice" doesn't require a galling display of ignorance of already-available words. Fun slang makes sense; but now we have an upwelling of slang that's just ignorant.
Here and there we see exceptions; take "rizz," for example. You can see that this comes from "charisma." OK, cool. But that's an outlier now.
> You can configure it with a GUI, or in XML, or using a type safe Kotlin DSL.
This is making me realize I want a CI with as few features as possible. If I'm going to spend months of my life debugging this thing I want as few corners to check as I can manage.
I've never had to spend time debugging TeamCity setups. It's very transparent and easy to understand (to me, at least).
I tend to stick with the GUI because if you're doing JVM style work the complexity and tasks is all in the build you can run locally, the CI system is more about task scheduling so it's not that hard to configure. But being able to migrate from GUI to code when the setup becomes complex enough to justify it is a very nice thing.
While true, we're at the point where JS is often used to pull static content to display anything useful at all. 20 years ago it was done on the server with PHP. Disabling JS ends up with a way worse result than it used to.
I would like to see more common browsers like Netsurf and Dillo. All of HTML 5, with CSS and stuff, but no JS at all.
Some promotion and branding and badges for how to build a site that contains no scripts at all.
I don't see the need for a new protocol and new clients. Just a plain ol' JS-free Web.
And, equally, something similar for the back end. No scripting languages, no PHP and no JS and nothing akin to them. Just native code, compiled from safe languages with bounds-checking.
No CMS, just dump text or markdown in a folder and presto you have a website.
I think we agree but you missed my point. You can create JavaScript-free websites (“documents”) and you can use a JavaScript-free browser, but there will still be websites with JavaScript (“apps”) around that your favorite websites (“documents”) will link to. You won't be happy with this arrangement until it becomes possible for your browser to cleanly separate the document-web from the app-web.
> The fact is that if you want to maximize your "market value", you still need to be _very_ good at React.
In some sense yes, but full-stack engineers are nowhere near the top of "market value". Frontend has a pretty hard ceiling on compensation. Past a certain level of advancement you'll never need to build a UI again.
If chatgpt is scraping the web, why can they not link tokens to source of token? being able to cite where they learned something would explode the value of their chatbot. At least a couple of orders of magnitude more value. Without this chatbots are mostly a coding-autocomplete tool for me—lots of people have takes, but it's the tying into the internet that makes a take from an unknown entity really valuable.
Perplexity certainly already approximates this (not sure if it's at a token level, but it can cite sources. I just assumed they were using a RAG.)
That's asking for the life stories and photos and pedigrees and family histories of all the chickens that went into your McNuggets. It's just not the way LLMs work. It's an enormous vat of pink slime of unknown origins, blended and stirred extremely well.
It's also worth noting that developers remain some of the most proportionately under-compensated jobs compared to the revenue we drive and we're all aware of it. It's the shareholders that need to justify their existence.