HNHacker News
TopNewBestAskShowJobs

soggybutter

106 karma · joined July 5, 2018

submissionscomments
soggybutter··on My first game with Carimbo, my homemade engine
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 platformers or similar, have a lot of expression through the systems that govern them. Whether or not a game feels good is fairly easy to figure out after spending some time with it, but understanding what would make it feel better and how to achieve it is a much harder skillset to develop. Obviously non-programmers can work out in high level terms what might improve game feel, but I think you can get much better results when you have deep understanding of how things work, what's possible, and what side effects may fall out of a given change.

That said, some of the most fun mechanics are born out of happy accidents involving interactions that weren't fully considered so it's definitely not a constant

soggybutter··on What if serverless meant no backend servers?
In 2024? What a ridiculous notion
soggybutter··on Ask HN: What would you do if you could start over?
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 make real progress
soggybutter··on Ask HN: What would you do if you could start over?
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!
soggybutter··on Ask HN: What would you do if you could start over?
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 it genuinely makes me sad almost daily
soggybutter··on Show HN: I made a game to improve my typing speed
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 letters on me all at once for some reason and I actually started to fall behind, but then it never happened again
soggybutter··on Strong static typing, a hill I'm willing to die on
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 that you don't have to muddy your test with a bunch of type checking logic and instead focus on the thing actually being tested is just the cherry on top.
soggybutter··on Inconvenient Truths about TypeScript
> 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 "quality"

I also agree that software quality is fairly subjective depending on your lense, unfortunately. For example, I wouldn't view quality as permitting as many people as possible to work at every level. Diversity of ideas is great, but I want those ideas to come from folks who have the skillset. If someone who roofs houses decides to pour foundations without gaining the proper skillset or picking up different tools I would view that as a loss of quality, not a gain.

> the term is time-to-market

I chose time-to-product fairly intentionally, because I think the benefits of something like Javascript start to rapidly decay once you start approaching any sort of product maturity. The problem is teams rarely optimize towards stability and quality until they have literally no other option

soggybutter··on Inconvenient Truths about TypeScript
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 zones, it's really hard for them to grow arms in order to use the saw.

I do acknowledge I have a lot of bias, though, because I work at a TS shop where the primary reason we continue to use it is because we always have. The longer I have to put up with it, the more I feel like this is a broken foundation to stand on

soggybutter··on Inconvenient Truths about TypeScript
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 beginner programmers who can't work on the backend without learning a new language, so lets put javascript on servers.

- CPU, memory, and bandwidth have continued to become cheaper, so lets just run everything in javascript because "we can"

- Let's hire javascript developers because we've made them the easiest to hire for

- It's too expensive to use a different technology because our entire engineering team is javascript developers

I honestly can't fathom the reasons why we've encouraged Javascript to eat the world, but I don't think there's any arguing that it has. Is this good or bad for business in the long term? My personal take is that it isn't, but there are enough variables to make this really difficult to say with any kind of certainty. It feels more like we've just:

- Lowered the bar for acceptable quality over time

- Convinced ourselves that the Javascript ecosystem is a one-size-fits all optimization for time-to-product

soggybutter··on Inconvenient Truths about TypeScript
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 tools. I would never try and use a hammer to saw a board in half, and yet that's exactly what people try and do with node/TS
soggybutter··on Fast
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 forced to in browsers
soggybutter··on I love building a startup in Rust but wouldn't pick it again
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 averaged around 144 req/s with a p95 latency of ~1s.

We average ~80 "instances" to maintain this level of performance. I have very little doubt that, if given the opportunity to rewrite this in rust, we could smash 10x perf improvements. Could we also get more perf out of tuning our python code better? Definitely. Do I think there's 10-20x improvement waiting to be uncovered? No.

Unfortunately (fortunately?) we're at a stage that it makes more sense to throw ludicrous sums of money at it than it does to ground up rewrite.

soggybutter··on Optimizing performance for 1000 units
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 static, compiled languages. Regardless of runtime. What blows me away is how unsafe the language is on top of being slow, and yet it's basically eaten the world
soggybutter··on The leap second’s time is up: world votes to stop pausing clocks
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
soggybutter··on The leap second’s time is up: world votes to stop pausing clocks
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" option when it comes to the human experience. Meanwhile, doing away with timezones also does away with a lot of complexity both in computing and other areas (e.g. scheduling across timezones)
soggybutter··on The leap second’s time is up: world votes to stop pausing clocks
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.
soggybutter··on Fast Software, the Best Software (2019)
The actual data that generates those pixels is likely much smaller than the pixels themselves, at least for anything hardware accelerated
soggybutter··on Ask HN: Why do startups avoid Java?
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't particularly fun or thrilling to write. If you're a founding CTO or a founding team of engineers, of course you're going to choose something more "interesting" for a greenfield project.

Java isn't as quick and dirty as other languages. I think this almost fully explains the prevalence of node, because after being stuck in the node ecosystem for two years, I truly can't imagine why anyone would choose to build anything substantial in node.

soggybutter··on Rust: “Explain GATs Like I'm 5 Years Old”
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
soggybutter··on I am a quite good bad programmer
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 structures they "learned". It's definitely not a given
soggybutter··on Tech CEO fired two engineers for having second full-time jobs
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 as they pop up, but at the end of the day you wouldn't continue to collect a paycheck if it was decided the value you bring was no longer worth the pay.

As long as you deliver acceptable value to your employer and show up to meetings you're expected to be at, time spent should be a total non-factor

soggybutter··on Ask HN: Why don't I see gold at the end of the remote working rainbow?
> 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 and 90% of the WFO argument is predicated on other people being there with you, I don't see how this statement could be possible. WFO absolutely want other folks in the office, whereas I don't see WFH feeling the same outside of some kind of safety in numbers (e.g. they won't force me to come into the office if a lot of my coworkers are also at home)

soggybutter··on Ask HN: How did you stop drinking?
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 advice with people who drink because the alternative is highly stressful evenings? Evaluating the history, I can see that drinking _eventually_ led to poorer health, but over the course of years also helped me to wind down and relax when I otherwise couldn't
soggybutter··on So you're using a weird language
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's only simple if you can check a lot of your previous experience at the door. Whether you're coming from a language with a more powerful type system (e.g. any other language with a static type system), or something completely dynamic, learning go will include a lot of friction. Despite it being a simple language on paper. I think that's part of the reason that python devs seem to have such success with it, because python and go tend to be focused on getting shit done over elegance.
soggybutter··on Gen Z never learned to read cursive
I would assume this has some effect on gen z signatures?
soggybutter··on Tell HN: Unpaid home assignments are not ok
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) I'm unfamiliar with. It sucks that you were ghosted, and I would view that more as an indictment on that company rather than the practice of a home assignment. To me there's no easier evaluation of skills you could ask for.
soggybutter··on GraphQL kinda sucks
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. Particularly the fact that you can write arbitrary resolvers for specific fields and include any amount of business logic you like. It blurs the line between GQL being an interface to your API and actually being the API, and invariably it seems that too much logic gets put into resolvers because it's so easy.

As far as I can tell, one of the best ways to use GraphQL is as a sort of RPC framework. At which point, my question becomes why not just use an actual RPC framework? Personally I find the field filtering and reduced network I/O to be overblown. Anecdotally, most of the GQL queries I've seen request HUGE amounts of data up front to reduce the number of overall requests that need to be made. Obviously not saying that's everyone's usage, but in my experience GQL has never really been much of a value add.

soggybutter··on Zendesk to be acquired
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 architecture onto a single server, using docker for example, would be considered a monolith. Or even better, any application that leverages a database on a separate server is no longer a monolith! That's way easier than rearchitecting your whole app.

I've never come across a definition for monolith in the context of software that had anything to do with the actual infrastructure employed

soggybutter··on Ask HN: What's is your go to toolset for simple front end development?
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 React, Vue, or any other big UI lib/framework
Page 1 of 2Next →