Ha, it really goes wild on comments. Just seen it write a 5 LOC function, with `return` and all, then add 15 lines of comments second guessing itself, then writing the same 5 LOC differently... In the same function body.
Not sure about Copilot, but the Cursor agent runs both eslint and tsc by default and fixes the errors automatically. You can tell it to run tests too, and whatever other tools. I've had a good experience writing drizzle schemas with it.
To some degree, yes, and I'd hope that other skilled professionals would take a similar approach.
Like if I wanted to add EV charging to my home, I'd hope the electrician would take the time to explain the different levels of charging, the breaker and wire upgrades needled, etc., find a suitable installation site around the house, etc., not just start hooking things up willy-nilly. Or that a HVAC person might talk about the pros and cons of heat pumps, or a doctor might discuss different treatment options, etc.
It's different from, say, being a line worker in a factory assembling the same part 10000x a day, or a fast food worker.
Sure, at some level we're all just "solving problems", but I'm arguing that a good dev thinks about the problem and possible solutions as a whole, and utilizes that agency to make the final output better, instead of just coding Jira tickets to spec and never saying a peep.
But that's my own bias as a predominantly frontend person working for small or medium sized companies where specialization isn't as extreme. Maybe at bigger companies and teams they already have many layers of UX/UI/design/management and don't need (or want or appreciate) a dev speaking up about any of those things. In my experience it's never that black-and-white and a lot of tickets and designs are ambiguous and require both professional judgment and some empathy to implement well.
Maybe that's why I prefer the generalities and of the frontend vs, say, hyper-optimizing a very specific database call.
100%. To an extent that's why I don't often freelance anymore as it's very easy to fall into a place where e.g. to build a booking app for a pet shop you need to become an expert in the field of veterinary.
Heh, it's funny, my partner is a vet tech and I keep thinking how interesting it would be to build a CRM for them and their patients (there is already an industry for that and some of the apps are actually decent).
Robust performance, error handling that's not stuck in 1982, and cross platform would be my guesses, but agree the OP could be more spicific as there are more benefits.
This comment implies you've not used Go. It really isn't equivalent to the NPM and dependency hell that's node. Or picking the number of workers in Gunicorn. Or.. C#?
I am not in any way “pro go” but it’s also very clear that JS is not the future. I know it’s where a LOT of people are right now but it’s been artificially pumped up to such a massive degree by being literally the only viable choice for the web for the entirety of its existence… and that’s starting to change and from both a technical, performance and development experience it is going to lose when that advantage goes away.
I assume you are talking about WebAssembly/WASM/etc?
Foreword: I'm not super up-to-date on the state of these things, I'll refer to to as WASM from here on out but if that's not the right term then substitute it for "whatever it is that lets you write code, compile it to something that runs in the browser that isn't JS".
I don't think the future is clear at all. Honestly, I'd expect to see some kind of "Compile your JS ahead of time to this WASM bundle" before we see web developers switching over in droves to some other language that can be compiled to WASM.
Unless you take over full rendering, my understanding is you have to provide some kinds WASM<->DOM bridge to interact with it, my knowledge may be dated.
I write web apps in Javascript (Typescript), real "apps", not "everything should be a SPA just because", and would be interested in anything that improves performance and/or developer experience. There are some data-crunching operations that might run faster in something WASM and/or some aspects that I'd love to share between client and server (and the server can't run JS in this case). That said, everything I have seen is a significant downgrade in developer experience for something that is semi-supported.
I look forward to WASM support maturing and the developer experience improving. To my knowledge there is not a Vue/React-WASM-type framework out there yet or any framework for building web apps in WASM (without starting from a blank canvas).
> To my knowledge there is not a Vue/React-WASM-type framework out there yet or any framework for building web apps in WASM (without starting from a blank canvas).
Not sure if these qualify, but these Rust web frameworks use wasm:
Here's the thing datastar isn't really a framework in the traditional sense (ruby on rails), you can bring your own backend and use it in a variety of ways. I use it a push based CQRS style, but you just as easily do request/response, hell even polling if that's your thing.
I think the happy place is somewhere in-between. Use JS to allow the user to build up a request/form (basically DHTML circa 2000), but use one of these hypermedia frameworks when interacting with the server. I think that these are successfully showing that BFFs were a mistake.
The government creates a new currency called $UBI, with the same legal tender status as the official currency for that country ($FIAT). I.e. people can use it to pay taxes, and people are required to accept it when doing commerce. Both currencies exist in parallel.
In the true spirit of ubi, everyone is entitled to an equal amount of it, and no one should be worse off by it. So they need to issue the currency new currency to give away.
They set up a system so everyone gets the same amount of money, at the same time, for maximum fairness. Everyone's income just goes up, equally.
$UBI officially has 1:1 parity to $FIAT, and this parity is used to calculate how much they'll need to "print" out at a given month. Let's say it's living_wage*population_size. That amount can be adjusted once a year by factoring in the government reserves built up exclusively from tax returns. In other words, the monetary base is a known, deterministic quantity.
They allow free exchange between $FIAT and $UBI, but the government does not officially exchanges it. They also allow people to set prices to their products and services freely.
According to the top echelons of YC, vibe coders are "1000x engineers". Add in 15-hour days and you can probably expect that team of six to surpass AWS in features by next month.
Fraternal twins for sure.
reply