How do you decide what to pick? I mean, I do Platform work on a large monorepo with many different interconnected services, and so I always want the implementation to be "correct".
1,926 karma · joined March 30, 2021
How do you decide what to pick? I mean, I do Platform work on a large monorepo with many different interconnected services, and so I always want the implementation to be "correct".
Surprised me it took so much scrolling to get to this.
Like, who reads all that crap?
- humans have a track-record of writing memory bugs
- memory-safe languages prevent such by construction
Therefore, what's the justification of not using a memory-safe language (as opposed to an unsafe one)?Then it seems you're not disagreeing with parent: they're saying "needle barely moved", you're saying "it will move".
They're talking about the present; you're talking about the future.
But do such acquihires usually result in higher salaries for regular (non-leadership) employees or? Also, what about NSOs?
Are these numbers supposed to provide any sense of the popularity if you're not often looking at npm trends?
Also, what's the long-term plan for YJIT.
Luckily, when I replaced the battery (got a lot from iFixit) and tightened all other screws, the keys magically started working again.
Saved me quite a few dollars.
> A software bill of materials (SBOM) declares the inventory of components used to build a software artifact, including any open source and proprietary software components. It is the software analogue to the traditional manufacturing BOM, which is used as part of supply chain management.
It's even worse than that: non-junior devs are doing it as well.
Byung-Chul Han would have a lot to say on this matter.
I would argue that by those measures, we are worse than let's say 50y ago.
That said, I'm trying to wrap my head around how projects like do work via wasm, given that wasm has so few types (numbers, arrays) and no I/O or system interface. I'm definitely missing something.
What kind of hardware would you suggest (preferably something with Rust!bindings). Is the one used in the original post a good starting point?
I've minimal to no experience with embedded.
M = Multi
---
C = Consumer
P = Producer