HNHacker News
TopNewBestAskShowJobs

jkoudys

882 karma · joined May 26, 2014

submissionscomments
jkoudys··on Your statement is correct but misses the point
That's the eternal struggle in software engineering, I'm afraid. In my experience, there's no product that performs better with a more complete feature-set than the MVP from two years ago that exists only in the CEOs imagination, and was never really used by anyone. It takes a lot of knowledge and experience to understand why the very good solution that I run off my laptop once every week or two isn't at all the same as one that could handle hundreds of thousands of non-experts running it every minute.
jkoudys··on Your statement is correct but misses the point
That's a good perspective. What's really lacking from so many of the "bad" comments is the context of the original comment. If you drop the context of someone using Python to process a moderate amount of text on a large, non-real-time system, then project your own context where it doesn't work, then sure python is not a good choice. If you can't agree on a basic context, or choose to force a context on them, then there's no compromise. Like in your teacher's example, you can't compromise between memory and cpu if you have no idea which you care about more.

They're mostly of the format "I like spoons because they can pick up liquids!", then the reply is "no forks are much better because they have tines to stab with!", without anyone saying if they want to eat soup or spaghetti.

jkoudys··on Your statement is correct but misses the point
True!
jkoudys··on Your statement is correct but misses the point
I've seen ironic trend of calling someone else's assertion "pedantic" as another way to polarize and shut down debate. That "confrontation quiz" attitude is very real, and it's often a way to avoid actually listening to someone else so you get to be correct.
jkoudys··on I can't keep up with idiomatic Rust
I _really_ felt that in JavaScript, especially es2015. So many updates came out at once, that people didn't realize many of the benefits they received from new features were now much less important because of other features that were included around the same time.

There was a huge rush to use classes, which was sugar around the prototype system, but happened when we also got spread operators, Object.assign, and property name shorthand. We could already easily express the concept of a class far more easily than we were doing before, but because it all came out at the same time it didn't really click for the community at large and a lot of what became idiomatic didn't really feel important enough for a language update.

Ditto with generators and async functions, which while merely a very specific application of a generator is far better known. Again, not sure we needed all this extra syntax so you can say `async function foo() { await bar()`, when `co(function* foo() { yield bar()` was already available (if co were simply added to the Promise object). We're also now tying the language to a very specific implementation, when the co approach is explicit about saying what's responsible for taking control from the yielded function (a Promise).

jkoudys··on “C is how the computer works” is a dangerous mindset for C programmers
Lots of languages suffer there -- eg there's no reason you _couldn't_ be a really excellent PHP developer who specializes in WordPress sites, but it's an uphill battle to prove you're a good dev because there so many bad ones in that space.

For that matter, most of the so-so devs resumes that come across my desk will list "HTML and CSS" as skills. Even among experienced devs, being legitimately good with HTML or CSS is extremely rare. I'd give my eye teeth to have a dev on staff who was an actual HTML expert (knows the w3c docs, can write clear, correct, semantic html using the right tags, organizes and expresses their intent, etc.), but since the barrier to entry is barely above basic literacy, so finding one is tough.

jkoudys··on Coronavirus cases by country – Two better ways to chart the spread of Covid-19
Stay out of the comments at the bottom of the article. Full of responses from people who didn't read it.
jkoudys··on Get Static
This advice is a bit misguided:

> get it down to static HTML and CSS and maybe a tiny bit of enhancing JS, and pare away every byte you can.

HTML is a language used for building your DOM. CSS is a language used for styling. JavaScript is also a language that can do those things, and focusing on the language used isn't going to help.

If the goal is to save space and power you can do it much better with JS. A lot of server side rendering, html caches, and static content is focused on good SEO and low latency, not small download size and power consumption.

You can fit a much smaller download into a stripped-down Gatsby site if you have a nontrivial amount of content. It also makes things like serving only much smaller versions of any images way easier. You can go even smaller with vanilla JS if you want.

jkoudys··on Why I’m Using C
You'll build to almost the same number of raw CPU cycles executed for the code, but probably build a better-performing game in a language with safer/simpler concurrency/parallelism. Ever since futures (concurrency) has stabilised, rust's my first choice on this. Pretty much all of his points not related to the sheer age of C apply; you can even get the 0-byte-overhead webassembly if you go no-std, though I seldom forego something so useful that's smaller than the loading-screen background.
jkoudys··on Why I’m Using C
Pretty easy to integrate C libs as unsafe calls with rust's FFI. You're definitely in for an uphill battle if you have to manage a bunch of decade+ old makefiles with hundreds of special flags for each platform under the Cargo ecosystem, though.
jkoudys··on Why I’m Using C
Rust will frequently build code that will run in a comparable number of cycles, but can often run even faster as soon as you introduce concurrency. Safety isn't just some crutch to lean on instead of simply being really, really careful in C. Concurrent apps need a lot of guarantees for memory safety, and it takes a lot of mental energy to figure out how safe you really are. C devs often go overboard and do more than is necessary as a result.
jkoudys··on Websites have evolved back to static HTML/CSS/JS files
Everyone looks at tooling like Gatsby+netlify to support their dreams of a JAM stack, but vanilla html/JS/CSS can do a lot written by hand too. I recently replaced a whole WordPress blog by saving it from the browser and cleaning it to the point where non-devs have an easier time updating it on GitHub than struggling with the mass of config pages and plugin shortcodes they needed before.
jkoudys··on Websites have evolved back to static HTML/CSS/JS files
Rust is great, but it's so young that even the ugliness we knew about from a couple months ago is better known than the ugliness of today. The latest stabilisation of async/.await has me hard at work forgetting all the pre-futures-0.3 stuff I'd learned.
jkoudys··on Rust Ownership Rules
It really is downright shocking sometimes how much gets caught by the rust compiler. It's the first time in my life when I feel like code is likely to actually work once the compiler comes back clean.
jkoudys··on Rust Ownership Rules
As someone who hasn't done much c++ in over a decade, but who loves rust, I often find the extreme focus on comparing to c++ to be a bit jarring and unhelpful.

As someone who's worked more with JS/ts/java, I find the borrowing system's guarantees far more interesting wrt concurrency. Yet that's often little more than a footnote in long articles about how rust is safer than c++.

jkoudys··on MVC is dead, it's time to MOVE on (2012)
Yeah - build out a graphql service on top of existing models, and you'll get a pretty clear picture about what the C ought to represent. You can find plenty of situations where the implementation of any of those letters is extremely thin: lots of services where the View is almost nothing (often just a JSON serialization of some of the models), or where the models are very thin. It boils down to a weirdly common, but deeply flawed, view that all the letters in your abstraction's initialism should be of equal complexity.

With Views, it seems to be easy for devs to understand that there is significant differences in the underlying approaches: are you organizing your views into page templates, serializing for some special client to consume, building components that compose one another, etc. I don't know why we can't wrap our heads around Controllers also having different approaches.

jkoudys··on MVC is dead, it's time to MOVE on (2012)
The one thing that will never die is developers claiming that something is dead.
jkoudys··on “We already store data. In a database. It works well”
#2 is the weirdest for me. You want a fully immutable, distributed widely by design, system for exploiting children? wtf? I'm much more concerned about the damage done to kids than about providing an additional, likely ineffective, way to identify a distributor.

They're also not seeing the flip-side of paying-to-edit and tracking all editors: it's trivial for a government to then use it do identify anyone they consider a dissident.

jkoudys··on F# Pipeline Operator in JavaScript with Babel
Same - the context variables are really for method extractions (e.g. the many times people used to call Array.prototype.slice on something). It's be easy in TS since `this` is already treated as special in function-arg contexts.
jkoudys··on F# Pipeline Operator in JavaScript with Babel
Been through that here, trying to get my whole dev env working nicely with both pipes and types. Very painful. I was surprised and a bit disappointed that pipelines seemed to be progressing years ago, then suddenly stalled. Nullish and optional chains are in ts already but pipelines aren't even on the horizon.

From what I hear from tc39 people, method extraction is one of the biggest must-haves holding this thing up. They want a nice way to bind contexts to an entry in the pipe. Ironically the difficulty of figuring this out for JS is keeping pipes out of TS, but it wouldn't be that hard a problem in TS which has ways to treat `this` as special already.

That, and the many competing proposals we already have. I'm fine doing an incremental rollout that doesn't need the placeholder `?` right now.

jkoudys··on F# Pipeline Operator in JavaScript with Babel
It's wasm. It could be written in Hindi numerals and unicorn emojis for all I care. So long as llvm can make sense of it.
jkoudys··on F# Pipeline Operator in JavaScript with Babel
I loved it, but came to an impasse when I had to decide between pipeline and TS. For a while I was running both a babel and TSC watch, where my babel build dir fed into the TSC watch. Dealing with two daemons when one/both screwed up, and needing to read errors in transpiled code, was annoying. What decided it was being unable to run prettier, since I could either use the babel parser for pipelines, or the tsc parser for the types. I'd be very happy if we could put pipelines back in and not break our tools and tax the two cores on my MacBook Air to the limit.
jkoudys··on Master of Orion
Don't forget the advantage in negotiations, too. It's basically charismatic without the leader recruitment bonus. It also lets you control ships (including star bases) after you capture them, making a battleship full of assault shuttles often enough to take a whole planet. Just the mind control of the planets alone would be worth at least 6 picks, and it's buffed on top of that.

Yet still, many players happily spend 8 picks so they don't have to choose between planetary missile base and automated factories.

jkoudys··on Master of Orion
I enjoy taking the opposite approach. Advanced start, impossible, Elerians, or any race with full negative picks plus telepathy. Rush out some cheap ships with no shields and piles of MIRVing nukes. Straight to the silicoid or sakkra (anyone with a good species and weak government), blast their starbase and mind control the colony. Immediately start shipping the population around using freighters, and the impossible difficulty works in your advantage, since you know have a super-species under your control. Properly managed you can outgrow anyone now. Keep the momentum up and steamroll anyone else who you can't be friends with and keep harmless.
jkoudys··on Ask HN: Which programming languages to learn in 2020 for an experienced dev?
I'm finding the very concept, and separation, of frontend + backend thinking has changed fundamentally in the past few years. There used to be a silly perception of frontend work as being somehow less-serious than the "real programming" you do on a backend. I'm sure you've found more and more in your react w/ gql work how little that applies now. Treating a browser like some kind of thin presentation layer there purely server-rendered html is very limiting.

We've also seen a major trend in recognizing the importance of strict(er) types with the excitement around TypeScript. Functional programming is also seeing widespread adoption.

The language that is best suited for including the browser as a target, taking advantage of an excellent type system, and applying functional programming concepts is without a doubt Rust.

It has the steepest learning curve, but once you get the hang of a few concepts, you'll be amazed that you're writing a systems-level compiled language with perf comparable to C, because a lot of code is more readable than JS. People go on a lot about the performance because it's impressive, but that doesn't even break my top 10 reasons to use rust. Everything is so safe and thorough, it's one of few languages where I write non-trivial changes that actually work the first time I run them.

jkoudys··on Low unemployment isn’t worth much if the jobs barely pay
Usually it's in the political context, as a cautionary tale about why you shouldn't fund healthcare/social programs/etc.
jkoudys··on Low unemployment isn’t worth much if the jobs barely pay
Having a heartbeat is a "pre-existing condition". It's vexing how often Americans will discuss treatments + checkups as though there's some chance that they _won't_ see their health degrade as they age.
jkoudys··on Low unemployment isn’t worth much if the jobs barely pay
It's doubly confusing, as you'll find unhealthy people have a much harder time earning the money in order to get well so they can work.
jkoudys··on Low unemployment isn’t worth much if the jobs barely pay
Yep. And I don't see it being fixed in the US, because the anti-single-payer crowd erroneously believes that US healthcare exists under a "free market". In truth, the budget per capita for healthcare in the states is actually _higher_ than in Canada. So Americans pay more for a lot less.

It turns out a few turn-your-head-and-coughs in your 30s is a way better deal than waiting for it to become a trip to the ER in your 50s.

jkoudys··on Low unemployment isn’t worth much if the jobs barely pay
America has a weird sense of superiority about its lower unemployment numbers vs Canada. The difference is the US, you basically need a job, or else you're one broken ankle, complex childbirth, or infected hangnail away from complete financial ruin. People being able to take extra time to find the right job is a good thing for the economy. Better than being driven by an abject fear of not having a job.
← PreviousPage 4 of 11Next →