skysight-inc/HackerNews huggingface dataset:
Sorry, but I have no knowledge and do not understand what "editing remote" means? What is the use case?

The source files are in a shared network directory, but VS code (the editor) is on my machine? Or is it something different?

Where would the compiler reside? Will the Compile/Build be executed on my machine?

Edit: found some answers: https://code.visualstudio.com/docs/remote/remote-overview
Bastardized TLDR: It's practically impossible to bootstrap a completely pure and trusted compiler (and hence computing environment) on modern hardware as all sorts of unseen firmware gets invoked before your first, manually-verified instruction.

I think one could keep following the turtles right down to the silicon...
Sure, but like, coal exists. At our current consumption rate there is centuries of coal still in the ground: https://www.eia.gov/energyexplained/coal/how-much-coal-is-le...

It would be rather rude to burn it in a post sealevel-rise world, but it is still there. Even after peak oil there would be electricity and heavy industry. It wouldn't be hard to lose advanced semiconductor manufacturing, (A war in Taiwan would do it) but halting production of advanced chips just rewinds us to 1980, not 1600.

PV production is ultra high volume and geographically dispersed. I don't see any way to take it all out without hundreds of EMP bombs or some kind of ultra-solar flare that fries all electronics worldwide.

In which case you wouldn't have genetic engineering. Or cities. What's left of humanity would be in small villages, engaging in subsidence agriculture.

You could set a novel in such a future, but it would be rather monotonous and unpleasant.
Most of these customer facing jobs will be abandoned or optimised away in the next few decades.

Front desk work could be done away with mostly by electronic systems (most of the time when I "check in" it's just picking up a ready made room card as I checked in online). You could even centralise the "talking to a human" part in a call center operating a number of hotels, who delegate to staff on the premises (house keeping, maintenance, room service, etc). Of course luxury hotels will still have humans.

Fuel pump operator hasn't been a job in most Western countries for decades, as you just pump fuel yourself (and often even pay at the pump). Is "EV charger operator" a job?
Not how language works dude.
> But if it is enough to survive on, then too many people who are capable of working will choose to instead just survive on it indefinitely.

This is one of the main benefits, if not the main benefit, of UBI. Someone’s survival is finally not dependent on working!

Right now, shitty jobs pay crap, because people have to take some job or starve. If you took away the starve part, millions of people no longer have to put up with a shitty job. If it really had to be done, the employer would be forced to raise the wage in order to attract people to voluntarily take the job. If UBI took care of everyone’s basic needs, then wages would have to rise to make it worth it to do a now-optional job. Would you flip burgers for minimum wage if UBI allowed you to live in an apartment and eat? I wouldn’t, but I might do it for $40k/yr extra over UBI.

This is a major goal of UBI, not a failure case.
Can also highly recommend Google (from first-hand experience). While there are pockets where this isn't 100% true, internal mobility is first-class so it's easy to improve things if you don't land well.
> The benefit of reproducible builds is that it's possible to verify that a distributed binary was definitely compiled from known source files and hasn't been tampered with, because you can recompile the program yourself and check that the result matches the binary distribution.

It's not just security. If a hash of the input sources maps directly to a hash of the output binaries, then you can automatically cache build artefacts by hash tag and get huge speedups when compiling stuff from scratch.

This was the primary motivation for Nix, since Nix does a whole lot of building from scratch and caching.
You could order replacement screens and try to fix it yourself. Depending on the model it's often cheaply available on Aliexpress or ebay.
Who mentioned anything about breaking existing code?

I already decided in 1992 that I don't want to use a broken language, unless when obliged by university work or work requirements.

Unfortunely I have to use software written by people that don't share that opinion and apparently WG14 also has a general policy that improving C safety doesn't matter.
I don't understand why people stop their trust analysis at flashable firmware. Somehow people can't trust their hardware's firmware, but they can blindly trust the hardware itself? Why? Would you even be able to tell if the hardware had firmware in it you didn't know about, let alone the fact that the hardware itself could be malicious?

This is why the whole thing seems like an exercise in futility to me. Just trust a reasonable base (e.g., including the OS) and call it a day. If you can't even trust your vendor to give you trustworthy firmware then find some way to invest $N Billion into your own fabrication labs to make your own chips in front of your face.
> Reproducibility is technically pointless, because you still have to trust the developer, and they can still add backdoors.

Builder != developer - and with reproducible builds, you no longer beed to trust the builder. CI is commonly used for the final distributable builds and you can't always trust the CI server. Even if you do, many rely on third party thingd like docker images - if the base build image gets compromised, code could trivially be injected into builds running on it and without reproducible builds, that would not be detectable.

As a developer, it would be quite reassuring to build my binary (which I already do for testing) and compare the hash with the one from the CI server to confirm nothing has been tampered with. As a bonus, distro maintainers who have their own CI can also check against my hashes to verify their build systems aren't doing something fishy (malicious or otherwise).
Keep in mind that if the additional costs are applied to everyone, prices can increase without one restaurant in particular being penalised

Demand is probably slightly elastic, but not that much (there are plenty of restaurants in France, despite very high cost of employment)
Isn't this extremely dangerous? Disk write caches aren't used most of the time, except on battery backed HBAs. And databases are typically configured to use O_DIRECT for a reason: COMMITs are supposed to be durable. We had this fight at a previous company when an engineer based database server hardware recommendation on a dangerously misconfigured database server, and did not consider the effect of caches. As soon as a safe configuration was used in production, performance dropped off a cliff, particularly on random IO. So the question we had to ask was: do you want to trade durability for performance? Or do you now have to carve up your databases into shards that fit the IO performance characteristics of the badly chosen servers you purchased, and waste rack space and CPU power?
can they already do this with all the data they have in github? Not that I would endorse it, but that sounds like better data for tracking. Instead of enforcing time you enforce activities.
These jobs are disappearing as part of the constant search for productivity increases. A front desk clerk will now spend their “down” time doing admin work for example
This needs Cloudflare. Ridiculously awesome free tier.
Completely true. Working has become a race to the bottom. For substanance, we should today be able to work three days for that matter. Volunteers for more are fine too. Problem is, that all economies must find common ground, or you will indeed get behind.
Well I expect it of my car, and it hasn't let me down yet :-)
I can’t figure out how wallets work — signed up for an account, went to Wallets, tap on Trust, but nothing seems to happen. Is it supposed to switch the (iOS) Trust app and prompt for my Ethereum address(es)?

PS: asking because I work on an iOS/Android wallet app and would love to provide integration if reasonable. So researching from that angle.
It doesn't matter as long as all competitors have to do the same. The price of a burger could go up and it wouldn't matter as long as every other burger goes up the same amount.
Maybe he wants to keep it affordable instead of profitable?
> The part I find particularly interesting about this trend is that both camps can't seem to fathom that the other could possibly exist

I don't think this is true. That being said, I think the most vocal are going to be the most evangelical (for either option).
What is your threat model? If you’re worried about some rando capturing the airwaves and snooping on your traffic, then you’re secure as long as you’re connected to a WPA2 or WPA3 encrypted network, which pretty much every hotspot supports. If you’re worried about whether you can trust the hotspot itself, then no - trust is a social problem, not a tech problem.
Someone who buys 7,000 pallets of what is effectively junk and then keeps it for 40 years is likely to have a strongly contrarian personality.
You get it into an orbit that will have several close encounters with Mars or other planets with atmosphere and you do a bit of aerobraking/thrusting on each pass.
OrganicMaps is Android and iOS offline maps for travel without trackers or ads
Serious Apple Bug Breaks iPhone Wi-Fi (SSID ‘%p%s%s%s%s%n’)
What is a capslock key, I only have ctrl and hyper ;)
Companies are avoiding hiring in Colorado
A lot of people clearly enjoy the actual hardware, the tinkering with it, the feel of the actual controls, etc. It’s not just about the software.
As far as I can see. These front desk jobs exist as theft/crime deterrent and to handle edge cases. Sure you could fully automate fuel stations but who is going to call the police when kids start spray painting the windows unless you have someone sitting at a desk watching cctv all day. And who is going to deal with customers who are trying to report something is wrong with a pump. These jobs have already been automated to the point that one person can handle a large store/hotel.
Sometime I don't get enough sleep when I start at 8am. It makes the result of work so much worse when you aren't rested. Sure, I could make sure to go to bed earlier, but life happens and honestly I don't live for work.
Fairly sure it's a piece of plexiglass with a LED strip around the edges. Normally the light would more or less bounce around inside the glass or escape to light up the environment. If you write on it the light hits the writing instead, giving it this cool-looking glow.
Yeah probably better off with a project Orion type approach.
Where I live garden lupine is classified as an invasive species, and purposefully spreading it is criminalized.
Idling at work is one of the most exhausting "occupations".
It's what the market demands in the end of the day and why I don't understand Japan too much (yet). If a company hires 4 people just for road signaling, and another 0, I'd hire the second one since it's going to be cheaper.

That's why I believe these market forces push to at-capacity, because if someone has spare capacity or a lot of profit another company is going to come in at a lower margin and win the market. Yes this leads to breaking at some situations that happen once every 20 years, but otherwise you die from competition so that's what we are stuck with.
Build an API in Rust (Part 2)
You were correct, I just tested with julia -t4 and that improved times by about a factor of 3.

N = 2000
27.137 ms (24 allocations: 61.04 MiB)
49.496 ms (3 allocations: 61.05 MiB)
4.597 ms (2 allocations: 61.04 MiB)

The CPU is a ryzen 3600 btw.
I saw something similar in Tokyo. It was at a telco office. A bell would ring (at 1pm IIRC) and an entire skyscraper's worth of office workers would get up and try to get to street level. Every day.

I was visiting a Western company that was renting a small space in the same building. Their routine was to never get caught up in the great migration (in either direction).
Shouldn’t the benefit of all our technology be the gaining of time for leisure and non-work pursuits?
Which drawing app do you use?
Early diagnosis of skin cancer at the price of a smart watch
Low margins are indication of saturated supply. If _everyone_ raise their prices, consumers would likely eat that, in my opinion, because people who really count food money usually don't go to restaurants anyway.
Architecture of the Playstation
On my keyboard, if I’m in Vim and want to search for λ, I type /λ. I type the λ with <right-CTRL>l.
(2017)

And then Microsoft gave up on developing their own browser engine and switched to Chromium.

And then there were only two competitors to Google's increasing subsuming of the Web.
I did go that far down, and there is a purpose. Reducing the scope of attack to "you must own a fab" is pretty great, honestly. Sure, it won't stop a perfectly placed nation-state from mounting a bespoke attack just for you by twiddling silicon doping on a wafer... But that's quite a bit harder and more expensive than "install an SMM rootkit".

And, if you do care about trustable hardware... There are bootstrapping and verification paths available there as well, depending on your threat model.

Or you can of course give up and declare all of computing fundamentally untrustable but still useful for some purposes. Like I said in the post, I'm glad for the existence of both the purists and the pragmatists in this space.
We need to separate two things:

1) Homelessness is never a desirable state and it helps no one, especially tourism which employs a lot of lower middle class people. Look at SF and Portland.

2) Just because homelessness is bad != not providing assistance and putting these people in jail. They’re two separate issues. I would vote for progressive issues that are highlighted in the article but I can’t stand progressives that try to demean others by calling them ‘cruel’ and gain moral high-ground over others. It’s unproductive.

We should never accept crime and shitty streets as an acceptable compromise. We can do much much better as the article indicates. I am disappointed at how many people in SF Bay Area think that tent cities are okay and they think they’re some kinda of a saint for caring for the homeless. If they really cared, they wouldn’t have let this problem happen in the first place. Anyone who is trying to solve the problem is looked down upon here which is mind boggling. Immediately labeling people as cruel without having a deeper discussion is not going to solve the problem.

We should strive to eliminate homelessness and not make it the new normal.
Taleb has absolutely destroyed his credibility by speaking at the "Coingeek" conference and sharing a stage with "Craig Wright"

https://www.urbandictionary.com/define.php?term=Taleb%27ed%2...
A system, where other people make more off your work than you do has pretty intrinsic problems.
Since we are on the topic of Japan and hotel front desk, this video shows an example day of a Japanese hotel staff who does a whole bunch of multi-tasking:

https://www.youtube.com/watch?v=qZsdm0RZ18k
I think what gets people so stuck on this problem is that nothing solves it. Everything is only x% of the problem, everyone is only a tiny contributor. We need to solve everything and all the percents add up to solving it.

Green energy is not the end of the solution but it is part of it. It's also quite a big part of it.
do not believe what is written in the media. in Russia, the maximum that can be done is to create a sculpture of a cock out of shit
Sure.

In that vein, "differently sized" should also be ok.
I read hopeful and idealistic (I’ve the same wish and hope, by the way) comments on HN and contrast it by thinking of CEOs and CTOs not even giving this news another second; laughing at it would mean it affected them in unimaginable ways.

Most of these “leaders”, especially in “startups”, have very short term goals - exit, acquisition, insane funding and valuations etc.

It’s not that they don’t think about employees burning out or lack of their well-being. They count on it. They know exactly what’s happening and they know that that 2<x> year old burning out (literally falling ill mentally and physically) after 7 month of hell, but wrote y number of functioning APIs, was a great success!

And that’s just software.
Then you end up with 996 system that is good for employers but not for employees or society.
Yes, but for how long though.

Many of these Japanese firms are many hundreds of years old, and will probably stick around for some hundred more years.

Being able to run a small business for 5-10 years is very possible, but there's no guarantee you'll be able to do that for 20-30-40 years.

We often hear about the success stories, when it comes to small businesses and startups, but there are unfortunately those that will fail after N years, even if they had some pretty good years.
Yeah but you still have to package up your app inside a piece of Java shit, have 70+ gradle files that break at every new release, sign your package, zipalign (what the actual fuck, the OS should do that) your package, ...

I mentioned C/C++/Python because the actual app would be much simpler and less bloated, not because of writing inner functions in those languages.
I find this debate interesting, but I can see this argument being used by both sides. Is your point that you don’t foresee external issues by buying like the supplier going under/the product becoming unmaintained or that you don’t foresee internal issues by building like some critical security oversight?
Show HN: Stock out watchdog for Shopify that forecasts and alerts stock outs
The complexity doesn't come from the emulation. It comes from trying to do the emulation efficiently based on assumptions about the behaviour of the other moving parts... which are also doing the same thing.

So, you've got firmware that is pretending you've got 512B/4kB chunks when really you have 16kB, and anticipating how the other layers might be doing things in order to maximize performance.

Then you have a filesystem/VFS layer, which tries to optimize its access patterns anticipating how the underlying solid state storage might be really doing things in 16kB sizes and how it might be optimizing 512KB & 4kB accesses to fit that.

Both those layers are dealing with filesystem journaling and how that might impact performance.

Then you might have a database, which is now trying to anticipate how the filesystem and the underlying firmware might be optimizing access patterns, and so it's trying to optimize to fit all that.

You also potentially have application logic that is trying to anticipate how the database might do things...

What you tend to end up with are many layers of redundant caching that are all working against each other in a very inefficient manner.
Most startups aren't engineering-bound though

Amdahl's Law
Well, it could be France instead since West Africa is French playground
> I really don't understand this argument; compromised infrastructure probably shouldn't be a regular occurrence, and even if so, automated killswitches seem like the vastly more preferable option, no?

I'm pointing out how complex implementing reproducible builds is. It introduces a bunch of really hard unsolved problems that people are very handwavy about.

Who will do the reproducing? You say that users won't be able to do it. That makes sense, because if they could, then reproducible builds would be useless! However, you also say they will be able to check if a build server is compromised at any time. In order for both of those claims to be true we will have to design and build a complex consensus system operated by mutually untrusted volunteers. That's really hard, and seems like it provides a pretty negligible benefit.
France: stares menacingly
He seems like a fan of the system operating for the good of collectors and not willing to put up with crap - the $5 item isn’t about the $5 but having to wait for someone who never showed up.
This argument is usually countered by pointing out that a lot of our production is mechanized nowadays, and this percentage is only increasing. Currently capital owners take the overwhelming majority of the gains from that, UBI tries to shift that more to everyone. UBI won't prevent more apples from being produced.

You rightly point out that that does not apply to supply-inflexible goods like housing in cities.
We Never Needed Stackfull Coroutines
So...most Android phones?
https://unevenearth.org/2018/08/the-social-ideology-of-the-m...
This is slightly different thing. Nix and NixOS are trying to solve multiple things, and that's what it might be a bit confusing.

Many people don't realize that, but if you get for example mentioned project from github and I do and we compile it on our machines we get a different file (it'll work the same but it won't be exactly the same).

Say we use the same dependencies, we still will get a different files, because maybe you used slightly different version of the compiler, or maybe those dependencies were compiled with different dependencies or compilers. Maybe the project while building inserts a date, or pulls some file. There are million ways that we would end up with different files.

The goal here is to get bit by bit identical files and it's like a Holy Grail in this area. NixOS just appears to achieved that and all packages that come with the system are now fully reproducible.
A novel server-side rendering web framework for Java
This is false. it is not a law. KYC is required for 3k+ and only in select countries. Brave is international.
Depending on device you have, you might be able to build a serial cable for it: https://wiki.postmarketos.org/wiki/Serial_debugging
I heard about these tracking software and I sincerely hope they won't get any more prevalent. As I see they are somewhat present in the contracting world.

I treat it as a total, humiliating devaluation of creative engineering work (and thus their identity!) to that of unskilled factory workers.
New Kind of Paper
Doesn't sound very liquid relying on a single person to follow through on that.
> You can theoretically construct an XREF:INDI: that points to the one individual, but it breaks every parser when the pointer appears in both the descendants, and other relationships

I read that as a bug in many implementations, not in the standard. Do you agree?
I'm honestly not sure what you mean by this comment. I used a real world example of businesses with high customer-facing labor costs relative to their net profit margins.

If you're getting into the everyone-deserves-a-living-wage side of things, that's a different conversation, one I tend to agree with, but is much more complex than the current discussion about whether current business could manage this if they operate with low margins and moderate customer-facing labor costs.
It disincentivizes people to ask for raises. That's a feature if you run a business.

I'm skeptical of the idea that it was accidental.
The "text of the memo" is really just the article's author not understanding the context of Steve Yegge's years-later retelling, from which that text comes. "His Big Mandate went something along these lines" (Yegge's words right before the quoted text) doesn't even imply there was a singular 'memo' involved, and definitely (and obviously) wasn't meant to say that the text was actually what Bezos wrote. So the footnote "Whether or not it existed in this exact form" is unnecessarily ambiguous about whether these were Bezos' words. They're clearly not - besides Yegge not saying they are, they're a dead ringer for Yegge's style and not at all Bezos'.