Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
soggybutter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
soggybutter
2y ago
Totally fine to paint in broad strokes, and I would probably lean towards that perspective myself. However there are some games that show off the programming more than others, at least in motion. Movement based games, like technical platfor
2.
▲
by
soggybutter
3y ago
In 2024? What a ridiculous notion
3.
▲
by
soggybutter
3y ago
My wife has suggested the latter a few times and it definitely seems like the most realistic approach. I have a small game engine I've worked on off and on again over the last few years, but it never feels like I have enough time to ma
4.
▲
by
soggybutter
3y ago
I've made several half-attempts at this over the years, but it always ends up falling to the wayside when life gets hectic. Maybe one of these days I'll finally push through though!
5.
▲
by
soggybutter
3y ago
I would've focused on game engine development and gone into the game industry instead of chasing the money in web/web-adjacent tech. It's almost impossible to make that kind of change now without taking a massive pay cut and
6.
▲
by
soggybutter
3y ago
I stopped at 1144 and 114. This could really use more of a difficulty ramp. After level 20 or so I really didn't notice it getting any harder and it sort of got boring. There was _one_ level fairly early on where it dumped a ton of let
7.
▲
by
soggybutter
3y ago
Good tests only render SST superfluous insofar as the person writing the tests is capable of never making a mistake. The thing about good static type systems is they don't typically make mistakes in the domain they work in. The fact th
8.
▲
by
soggybutter
3y ago
> Who is "we"? "we" is everyone in the industry. I recognize it's more of an evolutionary thing, it's just my stance that the current environment is pushing us towards an evolutionary dead end. > Define &
9.
▲
by
soggybutter
3y ago
I didn't really think you were saying they should be used for everything, but I do think discouraging branching out into better suited tools perpetuates using the lowest common denominator. If devs are never pushed out of their comfort
10.
▲
by
soggybutter
3y ago
EDIT: formatting This feels a lot like a self-fulfilling prophecy that Javascript just happened to be chosen for. - Javascript is "easy" and the only option for browsers, so lets teach it to beginners. - We have all of these begin
11.
▲
by
soggybutter
3y ago
This line of thinking is precisely why node and TypeScript are so pervasive. It has nothing to do with them being the right tool for the right job and everything to do with perceived lower barrier to entry and resistance to learning better
12.
▲
by
soggybutter
3y ago
Modern JS is a passable language only after a tremendous amount of time and effort was invested to retrofit it as such. For all of the purported isomorphic benefits, I still don't know why anyone would choose to use it outside of being
13.
▲
by
soggybutter
4y ago
My team helps run and deploy a python service that is entirely CPU bound. It accepts an input, performs some computation, and returns a result without any sort of I/O outside of the initiating HTTP request. In the past week it's a
14.
▲
by
soggybutter
4y ago
Most of my bitching that JavaScript is slow comes from node, which is quite far removed from the DOM. Fast and slow are relative terms, of course, but JavaScript's language features necessitate that it will always be slower than most s
15.
▲
by
soggybutter
4y ago
I didn't say no one ever has, just that there's a very strong negative reaction even when they don't have reasoning for it
16.
▲
by
soggybutter
4y ago
I struggle to understand how we benefit that much from the same wall clock times mapping roughly to the same times of day across time zones. It seems like there's pros and cons to both ways and there's no clear "better"
17.
▲
by
soggybutter
4y ago
I've wanted to do this for years. Every time I mention this to someone I get a surprisingly visceral reaction against it even when they can't think of any real reasons why this would be bad.
18.
▲
by
soggybutter
4y ago
The actual data that generates those pixels is likely much smaller than the pixels themselves, at least for anything hardware accelerated
19.
▲
by
soggybutter
4y ago
Java has a bad reputation for being bloated and/or slow. I find Java and Go to be fairly similar (both GC'd, both fairly high performance, both statically typed), and yet Go has a reputation for being compact and fast. Java isn&#x
20.
▲
by
soggybutter
4y ago
Things like GATs also allow those smart people to add sorely needed features, like async traits, which the rest of us plebeians can benefit greatly from
21.
▲
by
soggybutter
4y ago
Optimistically, you should definitely be able to assume this. In practice, though, I wouldn't. I've been in school with and interviewed many a college grad that had virtually no concept of how to effectively apply any of the data
22.
▲
by
soggybutter
4y ago
So knowledge workers are paid for their time, therefore they are explicitly _not_ paid based on their hours worked? You're paid for the value you bring. Sure, part of that value might be that you're available to deal with things a
23.
▲
by
soggybutter
4y ago
> There’s definitely no such thing as the WFO’er that wants to force their preferences upon others any more than there are WFH’ers doing the same thing. Given that the WFH crowd has no expectation of collaborating in person with anyone a
24.
▲
by
soggybutter
4y ago
I'm a little over a week without alcohol, but I drank every day because I have a lot of difficulty winding down and relaxing. I still do, but I've made the personal decision to prioritize my physical health. How do you square this
25.
▲
by
soggybutter
4y ago
More and more I think this idea has merit. When I was still deep in the go kool-aid it was always shocking to me how difficult it was for some folks to use the language. "It's so simple!", I would scream internally, but it&#x
26.
▲
by
soggybutter
4y ago
I would assume this has some effect on gen z signatures?
27.
▲
by
soggybutter
4y ago
Everyone's different, but I would happily take 6h of working at my own pace with full access to all of my normal tooling in a low pressure environment over 1-2h of high pressure speed coding using "tools" (web editors...ugh)
28.
▲
by
soggybutter
4y ago
I've only used GraphQL at my last two gigs, and didn't work with it full time. So there's a massive grain of salt. I think GraphQL is _mostly_ fine as a technology, but it seems incredibly easy to misuse and abuse. Particular
29.
▲
by
soggybutter
4y ago
If your definition of a monolith refers to a singular server, then I've never worked on a monolith in my life. Even the crufty old ASP apps I used to work on weren't monoliths. This would also mean that deploying a microservice ar
30.
▲
by
soggybutter
4y ago
Unless I'm misunderstanding you, Svelte can absolutely be published statically. If you leverage SvelteKit and the SSR it offers, then yes you need to deploy a server, but regular Svelte builds a statically deployable bundle just like R
More ›