HNHacker News
TopNewBestAskShowJobs

jkoudys

882 karma · joined May 26, 2014

submissionscomments
jkoudys··on OPML is underrated
We need a word for these snake-swallowing-its-tail indirect abstractions we keep building. I have problem X, so I solve with abstraction a. Then I have problem Y, so I build b on a. Then to solve Z I build c on b on a. Then we discover a problem that is actually just X again, but rather than use a to solve we build d on c on b on a to solve it.

I remember installing enterprise java beans to support my soap wsdl 16 years ago. Meanwhile shopify built a basic Rails app using http verbs and killed the product I was using.

jkoudys··on JavaScript Bloat in 2024
I'd never even heard of pornhub until you degenerates told me about it. I had to look it up. Apparently "porn" is short for "pornography"?
jkoudys··on JavaScript Bloat in 2024
Pornhub needs to be small. Jira will download once then be loaded locally until it gets updated, just like an offline app. Pornhub will be run in incognito mode, where caching won't help.
jkoudys··on OPML is underrated
XSLT was one of the things that brought me to React indirectly over a decade ago. I wanted to runs something like apply-templates (components) and that got me looking at XHP. That was the inspiration for JSX which became popular via react. Ironically I don't even use jsx anymore now that javascript has caught up, and a lot of what react does was really appealing from the declarative side. Weirdly so many of the "experts" are pushing very non-declarative approaches to it now. I'd love if xslt could achieve its stated goals, but like the rest of xml it's too academic and ignores obvious practical requirements.
jkoudys··on The End of Programming
Plain English is a terrible way to express ourselves clearly and unambiguously. That's why programming languages exist.
jkoudys··on How to succeed at Meta
I left big corporate tech a decade ago, and it was true then too. You'd get bonuses and stellar performance reviews for fixing big, high-visibility problems, or many small ones that amounted to little more than clients asking us to look things up in the docs for them. If you tried to help someone who was unhappy and at risk of leaving for another vendor, but not someone who plays golf with your boss's boss, you risk getting a DSAT from them, but no credit if you retain that client. If you fix the thing that prevents big problems, or many small questions, from coming in in the first place, you also get no credit. More likely, if you do something that brings 100 problems down to 5, you're blamed for those 5 that come in.
jkoudys··on WordPress 18
Maybe, but what percentage of those branding themselves "WP Developer" are decent? I've had to unravel a fair number of plugins where they'd crammed everything behind a single action , or under one big theme.
jkoudys··on WordPress 18
Last two WP updates I did were essentially downloading the site with firefox's "save site as", running prettier on it, and setting up a basic netlify for what's now a static site. HN is quick to talk about "the right tool for the job" about WordPress, but WP also has great branding which often makes it the choice when it's _not_ the right tool.

imho the best part of WP is the dashboard stuff, so headless WP is a good choice. It's also frequently hurt by PHP's heavy push on inheritance, which can be at-odds with what is actually a very good events-based architecture in WP. Sad part is that the very good events-based architecture is so overlooked, most people who have spent time developing in WP aren't even aware it has events.

jkoudys··on REST vs GraphQL vs gRPC
Often the rates I'll end up limiting in rest aren't even bottlenecks at all in graphql. like if I wanted to grab a relationship that hasn't been implemented with its own resource endpoint.

e.g. get all the comments in every article written by one author, I might say `/author/john smith` that returns all their articles, then run an `/articles/{}?include=comments` for each one. That'll run a separate query server-side for each one, which can get very heavy if I'm doing thousands of queries. On the gql this is trivial as `{ author(name: "john smith") { articles { comments `, but because it's one request the server-side fetch can be run _way_ more efficiently. We have dataloaders for the SQL written that'll collapse every big query like this into (often) a `IN (?, ?`... query, or sometimes subselects. Same concept works on any sql or nosql approach. So yeah it might be "a lot" data were it RESTful, but we're not going to bottleneck on a single indexed query and a ~10MB payload.

The real advantage I see for REST in that scenario is that it can _feel_ faster to the end-user, since you'll get some data back earlier. Running a small query on thousands of requests is slower, but you can display the first little one's result to the user faster than a big gql payload,.

jkoudys··on Facebook Says It Is Removing All Content Mentioning 'Stop the Steal'
The split may come from Pence, interestingly enough. It didn't take much for Trump to malign his VP two weeks from the end of his term. Pence was chosen to satisfy the evangelicals, who are another similar group to the MAGAs in that they're not the mainstream republicans, but enjoy enormous influence.
jkoudys··on Indian developer jailed for making unauthorized train ticket booking app
This is most Indian web apps, I find. The article is great because it ties it the well known failures in implementation to massive legal, bureaucratic, and cultural problems. India has no shortage of talented programmers. I find it hard enough to work with clients who want status reports every hour and change requirements frequently, I can't imagine ever getting anything done with the spectre of physical arrest hanging over me too.
jkoudys··on Indian developer jailed for making unauthorized train ticket booking app
You start by accusing him of using a strawman, then using an analogy which doesn't even remotely apply. It's closer to your neighbour selling you the rights to park in their garden, then you selling those rights to someone else. Far from a criminal, arrestable offence, so their point on the broad-brush of being "illegal" stands.

Even my closer analogy is still pretty far off and it's much more innocent. Maybe closer to charging a fee to use a very tricky to figure out parking meter.

jkoudys··on Git is too hard
Git's hard when you see googling for syntax as a failure in the system. If you see getting SO answers as working as designed, it's quite easy. The main learning curve is just the idea of everything being branched, which is an increasingly common concept in many spaces.
jkoudys··on Is Rust web yet?
Yeah, I probably have been a lazy member of the greater dev community because I learned a lot of these things but never blogged about it myself. Juniper for graphql is a big missing piece from that page -- gql is big enough as an alternative to REST that it ought to be at least considered, while RESTful services typically come baked-in because they rely so much on standard HTTP (so their use with eg actix-web is obvious). What I really found amazing was how we could write one struct, e.g. an Organization, and easily build them from JWT claims, SQL queries, graphql payloads, or POST params. With many other framework libraries, I'd really agonize over graphql vs rest, but because the types are so rigidly defined, it's very easy to write the definitions once and use them everywhere, so RESTful endpoints are simple to setup where there's a client demand for them.

An extremely cool new one is serde_pickle support (python's favourite binary serialization), which we're using to load tiny word-vectorization dictionaries in WASM. This lets lawyers collaborate concurrently on the same contract, and farms out the laptops/phones they're working on's GPU cycles to auto-draft the contract (e.g. type 8 words, and can see "85% chance this a non-disparagement clause -- here's some example language you can use. Here's some case law saying when it's enforceable and when it's not").

jkoudys··on Is Rust web yet?
My company Clausehound has completely moved its legal tech contract analysis and version control platform onto rust, and launched a couple months ago. It's been fantastic. We're a similar setup to a lot of the top links on there (actix-web over juniper for graphql resolving with sqlx). While the speed is incredible, the biggest improvement has been the types system. I've never had such an easy experience being able to pick and choose libraries based on shared traits - eg we could authorize on jwt using jsonwebtoken, load fairly complex migrated relational data into our nice models, and even wrote the crate phpass so we could keep some accounts created back when we were a WordPress blog working.

The strict typing in graphql has made dataloaders orders of magnitude faster. The same code that makes our business logic clear makes it easy to figure out if graphql needs to resolve all those nodes with individual sql queries, one against the parent node, build some `IN (?,?,?,?)` prepared statement, or resolve from cache. String manipulation is definitely a bit harder, but otherwise the experience as a web app developer has been amazing.

jkoudys··on Trump’s Taxes Show Chronic Losses and Years of Income Tax Avoidance
This is a HUGE distinction that gets glossed over because it's hard to see the implication from a headline. A lot of his critics pointing to his "bankruptcies" had focused on businesses going bust. So, fair enough, his casinos sucked, but knowing when to declare a business insolvent is a legitimate skill and not necessarily a sign of someone who is overall bad with money.

Taking on $300M against your own name is madness. What scares me the most is we needed personal returns just to figure that out. There's no way you can go into that much debt without significant foreign or less-legitimate lenders in the mix. The man's also in his mid-70s, so everyone must expect that if he dies next week, there's something they'll be able to collect from the estate. Combine that with how closely he's kept all his kids involved in his businesses and you have a man with everything to lose.

jkoudys··on Things I Was Wrong About: Types
I did Java dev for a while, after being C before then. I felt like everything needed a pile of typecasting in front of it to work, even though these were often objects for classes you'd think should all play nicely. I realized only after dealing with it for so long that Java wasn't supposed to work that way, but how things can work when well written, vs old apps where half the code is written by a long line of 4-month co-op students, are two very different things.

Ultimately I think people just weren't given any credit for making good, reusable types, because then the next dev who submits a better feature faster using your work gets a raise, but you look like a kook ranting about best practices who doesn't do anything "business".

jkoudys··on Things I Was Wrong About: Types
If most business-side people actually knew what weak typed languages meant for their company, I can't imagine so many of them going for php/js as often as they do. You're always one expression with a `$contact` instead of a `$contract` in it away from a cancelled weekend trip or humiliating sales demo.
jkoudys··on Things I Was Wrong About: Types
My personal favourite omnipresent php vars are `$data` and `$value`. Like, no shit, what else are you storing in variables?
jkoudys··on Cobaul: A COBOL to WebAssembly Compiler
I feel like knowing some COBOL would be a handy thing considering how much of it is still hanging around. My main problem is that it's easy to find toy examples of doing some simple things, but all the value is in supporting massive, decrepit old codebases. I wish I could find a good example of that with some descriptions helping me unravel it, so I could take on a bit of COBOL work with confidence.

I love WASM and I love being able to wrap legacy work up so it can be called with modern systems (I did an AS/400 driver so a decades-old but still updated DB2 could be queried by a Drupal Commerce site), so this project is exciting. Just wish I could connect the obvious advantages I see in this project and other stuff like cloudflare's announcement with something full of pitfalls.

jkoudys··on Cobaul: A COBOL to WebAssembly Compiler
I can't look past the syntax.
jkoudys··on I lost €4k in a Facebook scam
*your. This was the last straw. I've finally had enough of my OnePlus autoincorrecting me all the time.
jkoudys··on Feds: IBM did discriminate against older workers in making layoffs
I thought my team became "medium" when I went from managing two people to four.
jkoudys··on I lost €4k in a Facebook scam
Maybe it's because the banks are all pretty good and modern in Canada, but I honestly just don't get PayPal. My credit cards are all very easy to pay with, fraud detected quickly and easy to dispute, and many purchase types insured.
jkoudys··on I lost €4k in a Facebook scam
The people here posting about how clever/careful they are, which is why they haven't been scammed, are the ones I see as most likely to get scammed (if they haven't been already without realizing). You're best protection against being tricked is realizing that you can be tricked.
jkoudys··on C’s Biggest Mistake (2009)
Ah. If anything, the whole "rust as better than C for everything" thing is starting to hurt its reputation, regardless of veracity. People get so focused on its use in perf-critical applications they ignore its other strengths. eg I've never replaced C code with it, but we redid our whole PHP backend as a rust app, because it's great for rigidly defined business rules too.
jkoudys··on C’s Biggest Mistake (2009)
Ah. If anything, the whole "rust as better than C for everything" thing is starting to hurt its reputation, regardless of veracity. People get so focused on its use in perf-critical applications they ignore its other strengths. eg I've never replaced C code with it, but we redid our whole PHP backend as a rust app.
jkoudys··on C’s Biggest Mistake (2009)
futures is definitely the big one for me. Getting all concurrency fully on async/awaits is amazing, e.g. actix-web awaiting an endpoint calling juniper for graphql, with async resolver methods making async calls against my DB, without needing to spawn a single thread, is lovely. Still doesn't work as smoothly as that, even though on paper it ought to. Getting close though.
jkoudys··on C’s Biggest Mistake (2009)
One way rust's just a different tool for a different job, is it really doesn't optimize for knowing everything that's happening inside someone else's code. It's a great example of the difference in procedural vs functional programming, where in rust you mostly just care what your function args are and what it returns.

Nothing wrong with learning multiple languages, of course. C was my first professional language, and I spend most of my days in rust now. No shortage of rust devs who are big on C too.

jkoudys··on JSON
My demand for that too has slowed in the past couple years, mainly because it's getting easier to do more on the client. e.g. I don't need to upload an entire .docx file, if all my backend needs is ~50kB of values queried out of one of its contained .xml files. Not saying this is a _solution_ to any of the encoding questions, only that it's reduced my immediate need.
← PreviousPage 2 of 11Next →