skysight-inc/HackerNews huggingface dataset:
I use DigitalOcean's managed k8s to host quite a few services over the last few years.

There's definitely some complexity and learning curve involved, but it comes with some nice advantages for my particular use case:

- Low vendor lock-in: I actually migrated to DO from a different hosted k8s, and I was able to reuse the majority of my configuration.
- Reproducibility: your projects are derived from the resources you upload, so it's hard to end up with a setup that you can't easily reproduce (or migrate!) elsewhere.
- High flexibility: I can do some relatively strange things with e.g. routing without k8s batting an eye. There isn't really ever a point of "oh no, I've found something I can't really, do".
- I've found it to be cheaper than cloud managed services once you're hosting as much as I am.

More generally, I like the...standardized(?) style. It feels like a sort of "build your own cloud", but the blocks you use look like everyone else's, despite the total product looking a bit different for everyone. I can use k8s managed, in a business setting, or fully self-hosted, and the essentials still work the same way.

A lot of bad experiences wrt complexity I hear come from running the cluster yourself, but nowadays, distributions like k3s make this, dare I say, pretty easy. If you want to use. VPS, DO managed k8s is very nice.
You might double check which version you’re on. Might still be on v7.

> the industry should collectively come up with a solution that incentivizes app developers away from electron rather than hoping they swim against the current of incentive.

They have the financial resources to build it in ~Rust but still chose electron. It’s a mind boggling decision.
Good post, a lot rings true in my experience! Twitter is a uniquely good place to meet people, though it requires a lot of work and calibration to use successfully, and it takes practice to be yourself in a public broadcast medium. But I feel like curating a quality follows list and interacting with people you like online has very high ROI. And it's worth taking the initiative — asking good questions, planning casual events, proposing ideas for collaboration — even if not everything pans out, it's about increasing the surface area for serendipity, opening up more possible paths, planting seeds…
but does team have 1 IT/ data person?

Edit: sorry I see that you are the same person I was replying to. Then to understand it better, who is consumer of so vast amount of data?
What’s your concern, specifically? To me it sounds like understanding in detail how oauth works would make you feel much better about this.
If you catch all then you don't need the + anymore, right?
I haven't seen them be mentioned, another good option is to buy a thin client or multiple thin clients.

You can get them on eBay for <$100, they will typically have a fair amount of RAM and a quad-core AMD CPU (enough to outperform a raspberry pi pretty easily), and they will typically be on the order of <20W of power usage, meaning that even running 4-5 of them with k8s/Docker-Swarm won't murder your power bill.

Just an example: https://www.ebay.com/itm/154783701325?hash=item2409d3d94d:g:...

You can pretty easily install Ubuntu or something on there and treat it like a normal computer.
Suburbs are what actually trades off against pro-urban/pro—density though. No one builds a dense city in a rural area. They do build suburbs there, and then those suburbs face pressure to become denser.

I will push back a little on your claim that suburbs are different: postwar sprawl is a remarkably homogeneous product, the codes from jurisdiction to jurisdiction are very consistent, the home builders largely national chains, the businesses in the strip malls also largely national chains. I’m sure there are exceptions but really for such a big country with so many ostensibly different places and identities, it makes very little difference which sprawl-agglomeration you live in. “Local character” and distinctive building styles mostly belong to the historic walkable core districts. The suburbs could be anywhere.
I used to enjoy playing chess against myself so sure, I can see this working, why not
What particularly are you objecting to about Devault’s POV? I mean most of this thread and the article are based on the lack of generic data structures or complaints that Hare is not Rust. The complaint about lack of built-in data structures seems to be focused mostly on developer comfort, with a sprinkling of issues concerning possibility of bugs in implementations of specific structures. With regard to the continual comparisons to Rust, ala ‘memory safety’, if any model of software development outside of Rust’s limited paradigm is ‘bad’ then nearly all code in use today is ‘bad’. That seems to be an unsupportable position in the extreme.

I understand some people will not want or value any given piece of software or infrastructure, but the blanket pessimism is not proportional to the alleged detriments proposed by Hare’s mere existence.

Maybe I am just being overly sensitive to what I see as over reaction to someone’s programming language preference, but this is the reason I have never, and probably will never, release the language I made and use day to day to the public.
"Also, please note that I don't consider it unreasonable to not believe that collapse is likely to happen by 2030, so please, don't feel attacked by my beliefs."
- why write like this?

Parsing this I felt like Bighedd when questioned by the attorneys in Silicon Valley.

The author is convinced by this article: https://www.opendemocracy.net/en/oureconomy/deep-adaptation-...

However the article is mostly talking about recognizing the threat and adapting not that "Big collapse" is imminent.
The vast majority of users of music notation are amateurs, and being more friendly to amateurs would mean even more users.

The vast majority of decision-makers are experienced users with a vested interest in the status quo.

The issue is very similar to why corporate systems have such horrible user interfaces. The people making the decisions in IT aren't the normal users of the system. IT cares about features, integrations, and high-level analytics. Employees care to be able to sanely input their time sheets, file an expense report, or buy a stapler.

I'd like a system simple enough to use by all the kids in my local elementary school music class, much more than I care about what happens in the local orchestra.
Funny. Seems like these companies are not place to be. Surprise!
Phwewww... this blog post and all these comments ring so true to me way outside of contexts resembling software development or business that it seems to me it's getting at something very fundamental.

A corollary to this in my opinion is that if promotion is expected at some point, I think the business/organization/institution has a responsibility to try to facilitate people moving toward that through mentoring or at least clear expectations. If nothing else, it makes the expectations clear, which clarifies how those might be at odds with other goals such as what the blog poster is articulating.
My personal belief is that PoW assets need to go away, and fast. That being said, the top five assets (based on market cap) are all PoW - most laymen (read: statespersons) are probably only aware of the top two, and Dogecoin.
It's not a tax thing, long-term leases or colocation is a liability for acquisitions. (You could also build a revenue-positive company, but that's the loser way out, apparently.)
Prior to Android 11 no permission was required to retrieve a phone number via the API.
There's something magical about mechanical watches. Maybe it's just knowing that you have this perpetually winding machine on your hand (in the case of "automatic" mechanical watches).

Also knowing that the thing will last forever, take care of it and it will probably outlive you. Can't say that about an Apple Watch.

If you want a good mechanical watch that won't break the bank I suggest picking up a Seiko SKX (though prices have been going up), a Vostok Amphibia (might be hard with the ukraine conflict) or a Timex Marlin.
Vaultwarden is a free, OSS implementation of the Bitwarden server, and has no licensing costs. It's API compatible with the official Bitwarden client, which also has no cost. If the client supports the functionality, and server supports the functionality, you're in the clear. Bitwarden's documentation on features and licensing are only applicable to their backend products.
No, the root of the problem was death.
That sounds like a great use case of MQTT. Do you have any tips or references to copy your approach?

Is it easy to display the last message received on a collection of topics? It would make it easy to watch a custom summary of a large system.
In other words, "hire people who want to work hard for the founders at the expense of their self-promotion".
Some ideas: hire fewer people, well remunerated, but make normal pay increments guaranteed and promotions less frequent. Then there isn't such a glut of new engineers constantly creating an "up or out" culture, and people aren't laser-focused on promotion to win big. And lower the early 3 years' RSU allocations.

Basically, turn it into a marathon not a sprint.
Pandemic Technologies
It's the last stage of the second Dotcom bubble. The industry has been taken over by parasites and the well of innovation left over from the ARPA/PARC years is starting to run dry despite some of the better ideas having yet to have seen their heydey. It will be interesting to see what happens as the money-spigot dries up as the Federal Reserve starts to implement Quantitative Tightening over the next few years. I'm optimistic as all of this might, "reset the board" enough to slow trends toward digital enclosure. Worth looking at:

https://web.law.duke.edu/pd/papers/boyle.pdf
Much required! Thank you for sharing.
I just wish it would auto-fill my normal email in the username field...
Yes, this has been my observation as well. I also see this happening concurrently with what I call the "shiny object" problem. Developers have their eye on a shiny new library, framework, language, etc. and have a seated desire to use it at the expense of it being an inappropriate choice for the company.

I believe these two phenomenons are producing a positive feedback loop in the industry. Selected technologies address one challenge, but introduce complexity. The complexity becomes difficult to manage. So other technologies are incorporated to manage the complexity. In the midst of all this, core technologies are replaced, swapped out, or transitioned to under the desires of the dev(s). For example, switching from one js rendering library to another, while preserving the old legacy code. The complexity footprint keeps growing and it doesn't stop because the engineers themselves aren't entirely committed to the project. They can incorporate the new technology to the project, pad their resume, and bail to a new employer if things grow out of wack.
>Bitcoin is a digital currency

Nope.

It's more accurate to understand it as a store of value, like gold or art or baseball cards. All of which only have value because other people will give you fiat currency in exchange for some.

If it makes you feel better, Bitcoin was likely created by the US Government (unless you believe in Satoshi/Santa). There is around $70 billion in bitcoin sitting unused in the original wallet somewhere, something only the US Government could resist burning through. Once you realize the origin myth and its effectiveness as a tool for destabilizing other currencies and extracting wealth out of unfriendly countries by bypassing their currency controls, you realize the US Government backs it, so why shouldn't you?
I know some people are more sensitive to that, but the annoyance of managing 2fa seeds via some other app (that I have previously had difficulties recovering...) outweighs my actual perceived risk. Thanks for confirming

Edit: Based on the other reply to my comment-- are you using the Bitwarden self-hosted solution? I was primarily interested in Vaultwarden, the OSS alternative
Python expressions are accessible in [Hissp][1]. In [readerless mode][2], you're writing in Python anyway, so it's trivial. In [Lissp][3], you can inject Python code strings with `.#`. In [Hebigo][4], you just put parentheses around the whole thing.

[1]: https://github.com/gilch/hissp

[2]: https://hissp.readthedocs.io/en/v0.3.0/tutorial.html#hello-w...

[3]: https://hissp.readthedocs.io/en/v0.3.0/tutorial.html

[4]: https://github.com/gilch/hebigo#bracketed-expressions
This man is marvelous. Even though I know how top-notch he is at writing interactive blog posts, he surprises me with his quality every time I open his new blog posts. Bartosz is a huge inspiration for me.
A very simple language with low expressiveness leads to very big bloated codebase.

k8s is an excellent example.
a digital dollar? what? most dollars in existence today are digital. so why does bitcoin exist again?
I don't think it's about power. Because of the way the organization is structured, I am isolated from the IT department.

Moving me out brings no advantages to either part of the org. In fact, it's probably a disadvantage to IT because it has to burn three people from its allocated headcount. Where previously, it had a bonus person that didn't come out of the IT budget.
The company has 1 IT person and uses a third-party vendor for IT support. We have several data engineers and scientists, but we are not specialists as DBA or cloud infrastructure; it's just one very small part of our work.
Okta and OneLogin are both private corporations that have each existed for 13 years. Does your threat model include an estimate for how long they will stay in business? What if one of them puts the other out of business? Does your threat model choose a winner in that fight?

As far as paid services the possibility also is there that someday _you_ run out of money and have to stop paying them. They tend to shut down your access when that happens. Another financial threat you have to model.

These things don't happen when you use public key authentication.
I am not well-versed on self hosting but interested in doing it. If I run Bitwarden on a Raspberry Pi and if the Pi breaks (let's say it completely stops working), will the passwords be unrecoverable?
What are your experiences?

There are also Authentik, Authelia, Dex and gluu.

There was a bad review of gluu in Reddit.

https://www.reddit.com/r/selfhosted/comments/fxotbi/experien...
I agree with the sentiment about Slack being slow and bad. It’s not exactly the same as IRC though. There’s voice chat, screensharing, I can drag and drop video files without worrying about hosting, etc. People choose Slack over IRC for a reason, it’s just too bad it’s a private centralized thing written as a resource hogging electron behemoth.
[I don't read music.] From stories/videos I've watched on the topic, musician's don't so much read absolute notes but notes of a scale. A trained one knows their scales and can represent them with the letters A-G once each, using sharps or flats as necessary. I'd also expect them to know exactly where each note name/sharp/flat is on the instrument they play.

There's also an affinity for piano being a sort-of reference instrument pertaining to mapping of scales as it has the least idiosyncratic placement of notes compared to other instruments.

What about a scale that has lines for the white keys of the piano and larger spaces where black keys appear would be 1:1 with piano, but there would be too high a density of lines.

So how about we make the black keys the lines and we can have single spaces for single white keys and double spaces where two white keys intervene the black ones? That almost makes sense as the lines are black and the page/spaces are white.
If you also take into consideration the years it takes to go from junior to senior/experienced in the systems area, salary becomes a much bigger deciding factor. It’s not just 20k a year less for one year, its 20/30/40k less for as long as you’re mastering your area when you could spend less time mastering something else for more money.
agree, some folks just redo things because "I can do it a different way", that might be over-simplified the situation, but essentially it is for these folks.
the reasons could be different, resume, personal preferences/skills, even could be work politics ...
You can't do proper functional programming without garbage collected closures. There is a reason why Haskell has a garbage collector ... and it's not "the borrow checker wasn't invented yet".
I worked on one of those infrastructure services (like Bigtable). It was a huge boon to my productivity that the one version rule existed.

If we had to maintain 6 past months of releases, we would never get anything done. Since breakages in our client library were our problem, getting a months-old bug means that we can just tell you to recompile rather than figuring out how to backport a fix for you.

Hyrum's Law considerations got really weird, especially when people take them too far. I think this is based on the kernel idea of "don't break userspace," but its practical implications are nuts. Hyrum's law has killed infrastructure projects that could have made things a lot better, and has resulted in crazy test-only behavior being the norm.

One person on an adjacent team loved taking behaviors as promises (and he also had a reputation as one of the most prolific coders at G). We had to clean up his messes every time he relied on unspecified behavior. I pushed back on his nonsense a few times, particularly when he used an explicitly banned combination of configuration options that we forgot to check-fail on, but always lost. 1.5 SWEs on our team were full-time cleaning up after him.
On an old Dell Optiplex Micro:

- AdGuard for DNS blocking.

- HomeAssistant for all of my smart home stuff.

- Confluence for my wiki (back when you could get a $10 license, and yes I know it's overkill/unnecessary pain).

- Postgres (for Confluence)

- Nginx for reverse proxy.

I also have a Synology NAS (DS1618+) with a bunch of 10TB drives. The stock Synology apps are pretty decent and the entire package is polished compared to using something like FreeNAS. I use the built-in Photos app to manage my photo collection, ActiveBackup handles backups across all my PCs, and the Synology Drive software replaces Dropbox for me (complete with the ability to share a file via a password protected link). I run a dockerized version of SabNZBd/Sonarr/Radarr as well right on the NAS. Synology's CloudSync utility copies my most important files to a Backblaze B2 bucket.

I have the NAS connected via a 10 gig NIC for the NAS and a cheap Mikrotik 10 gig switch (with a gigabit uplink to the rest of my network). Combined with a QNAP Thunderbolt to SFP adapter for my MacBook, it's more than fast enough to use like local storage, including running VMs.
I'd have to look into it, but I think the whole reason for text vs. binary demarcation is the fact that ASCII text (not Unicode, old-school ASCII with valid characters 0x01-0x7F) could be sent over a 7-bit serial interface and binary needed that extra bit so you had to introduce overhead to make sure everything reached the other side. Because you might have had actual 7-bit serial (or less) teletypewriters connected in the 60's.
I don't buy that argument. ICs are massive. Way bigger in terms of number of schematic pages than any PCB. I think the problem is that PCB designers are used to having very "flat" schematics whereas IC designers always have a lot of hierarchy.

For example, the madness with the schematic he shows in that video for all of the by pass caps is something you'd never really see in an IC design. The cap would be placed in the schematic hierarchy either right at the voltage regulator or right at the circuit where its needed. But on PCB schematics you see that kind of thing all the time.

Part of the problem may be that with an IC you can easily simulate anything. The whole workflow is built around it. For a PCB, outside of using models for standard analog building blocks via spice simulator, it's a lot harder to verify your design.
Fixed supply -> almost certainly inflationary. It is only not inflationary if nobody ever makes a coin burn and nobody ever leaves less money in a that is worth less than a transaction to move it will cost.
Crafting accessibility on iOS, things our app got wrong
> They will demand revenue and ROI above all else.

I don't think this is true. They mostly demand growth over all else.
Reread my comment I wasn’t trying to prove a point. I explicitly stated why I included the quotes :)

I wasn’t going to repeat what the other comments already said: you are right but you are missing the point? Like you said:

> But it is only "less" apparent measured relative to other engineering fields... when viewed without comparison to other engineering fields

I don’t think any of the authors will disagree with what you just said.
I don't know how you can call this a slight of hand the title of the article is "Most Salvadorans have already ditched their national Bitcoin wallets", I don't know how you could make this more clear in an article title without making it too long.
Do other companies seriously not do this? I would think that is a basic security concept at this point. Then again, I've seen worse security practices at companies.
You can still often check to see if someone has an account for a service by just .. trying to sign in or retrieve lost password. You often don't need to have the password or access to the email to tell from the response if there's already an account registered for that email address.
> for example, the fact that lithium mines are an environmental disaster

Are they though? I mean, sure they are - all mining is to an extent, but not only are they relatively benign considering lithium is nowadays obtained from brines, not solid material, we don't need a lot of lithium in the first place - global resources excluding seawater are estimated to be around 80mln tonnes, meanwhile annual iron ore production is over one billion tonnes.
Not really? Promos incentive "up and out" culture, where people switch teams after getting promoted. Machiavellian managers respond by not promoting their best people, instead forever dangling the carrot of "deliver this and get promoted next cycle!".
That is eco friendly if you consider the co2 emission of making the car.
Yes it is because I can only wear one pair of socks and if he 1x price socks don’t cut it then 10x it is until we get to an acceptable level of comfort. Paying 1x for socks my kid won’t wear provides me 0 value where as paying 10x but having the kid wear them just means that this is how much socks cost.

As to why they are better the toe knit eliminated the seam and hard spot where cheap socks terminate. The fabric wicks moisture better and get material is less abrasive. The knit and fabric all add significant additional cost to the fabrication process. Look up some videos on you tube on how socks are made.
Only because Perl takes heavy inspiration and syntax from Unix shells.
So what you're saying is basically: "he's asking for it", right?
I'm far from being proficient in rust but my productivity writing crud apps in it is pretty good (just throw some Rocket + SQLX and you're flying).

Rust is a very high level language, it's not like writing assembly. You rarely run into complicated situations with the borrow checker when writing trivial crud apps.

The ecosystem is not as mature for web apps compared to other languages, so it may be more efficient to pick something else, but ultimately the most important factor (when building trivial stuff) is picking a language you and your team are comfortable with.
Whether that's Rust or node.js, it won't matter much.

If I were to make something else which is better supported in Rust, eg. a videogame, using bevy + ecs would run circles around a bunch of other languages and their game frameworks.