Quoted post unavailable.
Tell me you don’t know how venture capital works without telling me you don’t know.
181–190 of 397 posts
Quoted post unavailable.
Tell me you don’t know how venture capital works without telling me you don’t know.
I played with an early version of Deno a few years back and it was already way more comfortable to use than node. It's a real counterexample to second-system syndrome. The only reason I didn't continue was a lack of ARM support.
I had a very different experience. I very much wanted to make it work, but trying to use it with existing npm packages and import maps was incredibly painful, and I ultimately switched over to node for that project.
Who validated this idea and with what measures?
Seriously my biggest pet peeve with both deno and node.js. In every other REPL I've used this is basic functionality. When I talk about this to JS people they look at me like I'm from mars.
Interesting how this will play out. It's an ambitious goal to consolidate client side and server side javascript ecosystems which is quite fragmented today. On the other hand, this may only increase fragmentation further by introducing another target to develop for (wait for transpilers that can automagically convert between deno and node code). I will always look at javascript as this problem kid that cannot get its…
https://xkcd.com/927/
Quoted post unavailable.
Let's say a company were to adopt this tech over Node, well, it seems like it would be slightly better, but probably not much of a game-changer.
I'll leave it to y'all to talk about what tech is truly interesting as I don't want to seem ideological/biased, I just don't see how Deno is particularly notable.
> Early in cloud computing, virtual machines were the compute abstraction […] This is funny to me because serverless sounds to me like the return of PHP (etc) shared hosting. What's old is new again?
It’s amusing to see a whole generation of senior developers (“senior” as in 5+ years of experience) that haven’t experienced web development without React[0] and who proceed to reinvent PHP/ASP.NET/RoR. [0] Used here as shorthand for “modern js driven development”
Earlier quoted context omitted.
I like TypeScript and would like to write backends in TypeScript. I'm coming around on Elixir. I never want to write Go that interacts with a database again. Rust seems complicated. I don't think I'm smart or committed enough to get anywhere with rust.
> I never want to write Go that interacts with a database again. Why? I’ve been using sqlx and it seems fine.