Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jkoudys
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
91.
▲
by
jkoudys
6y ago
It seems like they're trying to solve a problem (manual destructor call to free memory) that is important in other languages but not rust on account of borrowing. Even in the author's examples I feel like it's a problem direc
92.
▲
by
jkoudys
7y ago
Not quite at that level, but rust does have OsStrings (managed the same way as the OS, often but not always utf8), and CStrings (basically just byte buffers - just like c likes). There are special rules around inclusion of nulls and null te
93.
▲
by
jkoudys
7y ago
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 imaginat
94.
▲
by
jkoudys
7y ago
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,
95.
▲
by
jkoudys
7y ago
True!
96.
▲
by
jkoudys
7y ago
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 actuall
97.
▲
by
jkoudys
7y ago
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 i
98.
▲
by
jkoudys
7y ago
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
99.
▲
by
jkoudys
7y ago
Stay out of the comments at the bottom of the article. Full of responses from people who didn't read it.
100.
▲
by
jkoudys
7y ago
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
101.
▲
by
jkoudys
7y ago
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 stabil
102.
▲
by
jkoudys
7y ago
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 eco
103.
▲
by
jkoudys
7y ago
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
104.
▲
by
jkoudys
7y ago
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
105.
▲
by
jkoudys
7y ago
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
106.
▲
by
jkoudys
7y ago
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.
107.
▲
by
jkoudys
7y ago
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 bor
108.
▲
by
jkoudys
7y ago
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 th
109.
▲
by
jkoudys
7y ago
The one thing that will never die is developers claiming that something is dead.
110.
▲
by
jkoudys
7y ago
#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
111.
▲
by
jkoudys
7y ago
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.
112.
▲
by
jkoudys
7y ago
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 opti
113.
▲
by
jkoudys
7y ago
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.
114.
▲
by
jkoudys
7y ago
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,
115.
▲
by
jkoudys
7y ago
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 sh
116.
▲
by
jkoudys
7y ago
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 (anyon
117.
▲
by
jkoudys
7y ago
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 progra
118.
▲
by
jkoudys
7y ago
Usually it's in the political context, as a cautionary tale about why you shouldn't fund healthcare/social programs/etc.
119.
▲
by
jkoudys
7y ago
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.
120.
▲
by
jkoudys
7y ago
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.
More ›