By practically any measure all of the things you've listed have been wildly successful.
10,008 karma · joined September 23, 2014
By practically any measure all of the things you've listed have been wildly successful.
I'm okay if you batch writes, I'm okay if you offer a low-latency mode with less durability, but by being unclear about this it just feels like a scam.
It works great and I've seen many teams gain significant productivity when collaborating in a monorepo with public bits.
If you're even toying with an internal monorepo you owe it to yourself to give it a try.
Having a public repo as a dependency for your private corporate repo is a pain in the ass development-wise. Having a tree of such dependencies is a migraine.
It works in all sorts of places too! Like negotiating a job offer or a raise or promotion or time-off. It also works outside of the workplace such as following up with social acquaintances ("hey let's play tennis sometime").
It excels at identifying the party unwilling to commit. And in my experience the sooner you figure that out the better.
> all the bluetooth MAC addresses that was seen by the Echo device in the home around the time of the murders
which is just not how this stuff works. I'd believe it if, say, debug-level logs were being recorded locally. But that would be an incredibly stupid way to burn through your flash storage.
But that's besides the point. A record of the last date of connectivity for trusted devices is an entirely different thing.
I'm interested in evidence that this type of data extraction took place. I'm not interested in speculation.
https://raw.githubusercontent.com/JohnEarnest/Decker/refs/he...
I've read and written a lot of C over the decades but this borders on being an IOCCC entry...
This smells like an urban myth.
There's bureaucracy of course but the mission is clear. Highly recommend working with them in any capacity.
AIUI in the US you can't do much to protect the visual shape of the font e.g. I can hand-trace your letters and make my own font and do whatever I want without issue.
I posit that it is perhaps more laborious to untangle those abstractions than to just write your own.
It's like improving the lighting in your house by going to the breaker panel and flipping breakers and splicing extension cables that you run up your stairs and down your halls.
This was never important. The important part was always knowing when to use them.
But this is so mundane it bothers me in a way I find surprising. It's more about how they made some questionable choices in the past and how they finally paid off that technical debt. Is it interesting? Perhaps I am just getting old and jaded.
What I find odd is how light TFA is on actual details as to what it is they shipped.
This is the kind of thing I'd ship internally to the org as part of a weekly update or something, but not what I'd expect on a public-facing corporate blog.
It's full of technical details, but I'm really not sure who they're for. There's nothing particularly novel or impressive. If anything the fact that it took them this long should be embarrassing. They pad it out with a table of stats that are just kind of meh? Congrats I guess for releasing something without burning the house down?
As an on-and-off customer of theirs I tried to quickly skim for some of the details that would impact me, the theoretical end-user, but the vast majority of TFA is just about how they pulled off this apparent feat of engineering.
I'm not trying to be pessimistic, and I don't fault the author (but I question the culture). I honestly don't get who this is for.
For the record this is something they should have had... at least six or seven years ago?
With Software in particular, I often encounter designs that copy a pattern from another popular piece of software, but without critically thinking about what the pattern is for or if it's even appropriate for their system, or even worse, assuming that because it exists and is popular that it must be good, when in fact it's terrible.
If recreating someone else's creation truly learned us, I believe the world would be a tremendously better place.
I used to run a lunch study group where we took some old crusty load bearing software, read the documentation thoroughly, and then dissected it, reading source and comments and trying to distill what it achieved well separate from what it achieved in spite of itself.
We learned a lot.
My point is that if you care deeply about what is being installed in the image, size, dependencies, bloat, etc. then perhaps using the NixOS abstraction is the wrong approach. Instead of building "down" by taking things away, build "up"
If you had have supported API key scoping then I'd have a ton of businesses/startups running on you. As it stands currently it's difficult for me to recommend you to orgs that are scaling up. Compliance in particular was the biggest issue. For one-man shops it's a no-brainer.
In your defense, Cloudflare has historically also sucked in this area.
Anyways, I'm looking forward to this feature!
It was at this point I began to question the entire exercise. If you don't want nix to even be installed, do you really want NixOS at all?
It would probably be much simpler to just build an image from scratch with the packages you want, composed in the way you want them, rather than contort the NixOS "UX" to produce the image you want.
At the end of the day you need some cross compilation just for board bring up.
If you're playing with some platform for which this has already been done, then sure, but that's not really the "normal" way of doing embedded.
I know a founder who has been building in public and it has had zero impact on his inbound.
Dear ImGui [0] is without a doubt the most prevalent immediate mode UI library. It does not have native accessibility features, but that hasn't stopped companies such as Intel, Meta, IKEA and Google from shipping products built upon it. It's also used in a ton of games.
Calling Dear ImGui a toy project at this point would be like calling Unreal Engine a toy project.
It's a shame accessibility support is not more widespread, and furthermore it's a shame that it is so laborious to add it.