skysight-inc/HackerNews huggingface dataset:
This is the same Jeff Varasano that is an OG speedcuber [1] and author of the book Jeff Conquers The Cube in 45 Seconds, And You Can Too! [2]

[1] https://youtu.be/0VfGnvHRXu0

[2] https://www.amazon.com/dp/0812870972
I recently deleted my Twitter and Reddit accounts. Both services seem to rely on an outrage->comment->outrage cycle to produce engagement, and I decided I didn't need to encourage more outrage in my life.

It's been good. I recommend it.
Analysis that covers points that were almost certainly on the whiteboard of Waymo of risk factors before the first line of code was written is weak analysis.

I’m gonna go out on a limb and guess they considered this a decade ago and have a reason to think these aren’t a long term problem.
I've read the English translation of that book. Quite simply, the best history of those wars (which could be called the real First World War, if anyone thought to name it as such), period. Hands down.

Strongly recommended!
> So then I realized that they were brain washed by the company internal communication to feel that anything annoying for Google was bad for them personally!

I think your interpretation of this experience is incorrect. Their visceral reaction was against leaking specifically, not negative information generally. Part of the propaganda behind TGIF, the internal newsletters, and so on is the idea that this inside information is part of what makes you special as a Googler.

> "...we hate so much the person that did that, that we would have like to have him dead."

While I'm sure you caught a big fish that day, I'm also sure it wasn't that big (come on: the retelling of this anecdote does not need quite that much exaggeration).
This is the case where you may be empowered to layout the values of being the knowledge expert for this to your management and give them buy in to have you be the owner of the product from a tech perspective.
Where "NY style" means really very "NY style": thin and charred. If that's your taste, go for it...

But for those more into the traditional original bread-like Neapolitan style I strongly suggest using a sourdough based dough, like Tartine's[0]

Bear in mind: this is cooking, not engineering, not math. And, unlike New Yorkers seem to believe, pizza wasn't invented in the land of burguers and hotdogs.

Wherever there are Italian immigrants there are variations in pizza all over the world, from Chicago (deep dish) to Sao Paulo (stuffed border, "coroa de pizza"), from Liguria (piscialandrea) to Sicily (sfincione), from Rome (al taglio) to Naples, etc.

[0] https://food52.com/recipes/64201-tartine-s-pizza-dough

Edit: to open your mind I'd suggest "The wild pizzas of Southern Italy": https://www.bloomberg.com/news/features/2018-03-15/the-wild-...
True, my old LG TV UI kept getting slower and slower with each update, finally I stopped applying updates and switched to a Roku.

Though the good thing is that I can't see the carcass of the old SmartTV laying around, the TV stays connected to the Roku so unless I accidentally hit the Channel up/down button and switch it to TV mode, I never see the LG SmartTV features.
The Dream Economy
In the dream economy, Musk is a technological visionary in the way that Nelson Mandela was a moral visionary in the 1990s. Musk’s status as one of the world’s richest people suggests we — or at least the markets — are prepared to place our money where Musk’s mouth is. Adding to the economic heft of his vision is the fact that even NASA is looking to him to lead the way. Since the company has indeed chalked up genuine successes, why shouldn’t we believe that Musk’s dreams about Mars will come true?
How do you make that kind of calculus though? Presumably Twitter will want to stay around for a very long time. If people like BTCOG take away a negative experience from it then doesn't it seed a future negative opinion of Twitter?

10 years ago when a government banned Twitter it was almost universally seen as bad. That's probably not the case anymore. Will it be worse in the future?
I think it's not a good idea. The intention is good, but how do you justify the decisions? It seems that the company would be easy to sue whenever a new study comes out claiming x is good or y is bad. It just seems like it would turn into the arguments in the recent 'SUVs kill' thread.

https://news.ycombinator.com/item?id=28269342
Firefly Hires Former SpaceX, Blue Origin Engineer as COO
> The problem is in the real world it’s close to impossible to tell the difference between getting work done early and the task being easier than expected. Same the other way around.

I don't see why that's a problem, provided there's not a lot of constant sandbagging when giving estimates.
>> but income taxes have continued to fall in spite of such bailouts, suggesting that no one actually had to pay for it.

I would strongly disagree with this. Taxes would go up with fiscal bailouts, not directly with monetary bailouts. A huge amount of the bailout was via monetary policy -- i.e. "print money and buy bonds to drive bond prices up and rates down."

We all feel it in the form of asset bubbles. Some people benefit (asset holders) while others lose out (young people, those without assets, renters, fixed-income retirees with almost no yields on their 401ks.

Taxes are a very simplistic way of judging payment.
Registration for Cisco DevNet Create is now open
It's because most stuff that engineers and DS work on is to make money for a company. Most of the stuff is internal tools, something used by internal staff, etc. And when you "finish" the job it's not something physical and hard that you can say "wow look at that, look at what we built".

So basically you're working on a team without much autonomy (there's only so many ways to fit in your contribution or your model), there's very little connection to the end product even though you worked hard, and most of the time you're working alone just coding something out.

So:
1. Little autonomy
2. No grand physical end product
3. Little deep social interaction
I have a plan to write a book on how to write reactive applications like that. Mostly collection of observations, tips, tricks, patterns for reactive composition, some very MongoDB specific solutions, etc.

Not sure how many people would be interested. Reactor has quite steep learning curve but also very little literature on how to use for anything non-trivial.

The aim is not just enable good throughput, but also achieve this without compromising on clarity of implementation. Which is where I think reactive, and specifically ReactiveX/Reactor, shines.
That's not really what's being talked about, though. The fear is that if you don't connect your TV to your wifi network, it will have a secret, hidden LTE radio that it uses anyway.

It doesn't seem that Huawei is being at all secretive about this; they are advertising it as a feature.
The premise of the article is incorrect. Waymo has not “solved the self driving problem”.
I’m not sure the US really sticks out here much? Every country (democratic or not) uses PR to shore up support for its efforts.

Canada has it’s “peacekeeping” schtick which it uses to sell troop deployments to the public. The US uses it’s “defense of democracy”. EU will use “human rights” as it’s cull (whether or not that’s truly the goal).

And they won’t just use those messages on their own people but others as well. Look at the South China Sea situation and how countries desperate for Western help to counter China message it. Or Taiwan for that matter.
Terrible headline. Should be something like:

Pfizer CEO says a coronavirus variant is likely to come along that is resistant to today's vaccines.
As a tangent, what's interesting is whether `mount` shows the mountpoint.

If you cd into a snapshot on FreeBSD it does not get listed in calls to `mount` but does on ZoL.

edit: i have not tested this since FreeBSD rebased on ZoL
The entire entire leadership team just quit and then they announce this?

That makes me worried this was rushed
I’m not aware of any HD maps built entirely automatically. As soon as manual steps creep in, the cost skyrockets. The backhaul and processing power required for updates can also be staggering.
even though you're probably right on the first part, the second part is false. while most NAT implementations operate as you describe, called "port-restricted cone NAT", some implementations allocate the external port only for a specific destination address, called "symmetric NAT".
How much doe. Over 150k? Over 230k?
> Rack mount hardware is almost always expensive, loud, and power hungry. I just have never seen the point of building a home lab like this.

Rack mount is just a form factor, so that generalization doesn't make sense. You can get pretty much any capacity systems you need in a rack case, including small cheap ones.

When I got tired of having systems in various different case sizes and a mess of wiring and switches etc, I moved everything at home to rack mounted.

Now literally everything is one big box (16U rack), with just power and network cables going in. All the computers, network switches, wiring, UPSs, KVM switch and monitor. Very tidy, very clean.

The computers themselves are cheap, quiet and efficient, since I don't need any monster servers at home. A couple are Atom-based (<20W total), one Celeron and one desktop AMD-based (forgot model). Same level of hardware I had before rack mounting, but now a lot neater and more organized.
So that's what they settled on? Kent tried to introduce it while I was still there and the pushback was so severe they decided not to do it at the time. I think the initially proposed retention period was shorter than that though. I could live with 18 months, but shorter than that cuts into all sorts of business processes including the all-important performance review cycle (AKA "perf"). I do think it's detrimental to the business of writing software though. I quite often search for emails from years and years ago, as well as mail "notes to self" to be able to find them later.
Looks interesting, but it looks like it might be hard to integrate with, or use in a batch fashion. Gpg has options like "--passphrase-fd", "--batch", "--yes", and so on to address these things. Not that you need to implement it that way, but some way to accommodate batch mode and integration.
> ... it may be prohibited to fire an employee for requesting better working conditions, but if an employee refuses to serve a particular customer because they don't like them, that would seem to me a quite reasonable reason for termination.

I agree completely. However, if an employee doesn't refuse to serve a particular customer, but instead voices to management that they do not want to serve that customer, I don't think it should be ok to fire them. In this case, it seems to be less about declining to serve and more about voicing an opinion (showing a petition throughout the office).
I disagree. Only the most simple basic highway lane keeping is commodity and that is only small part of overall driving.
Hosted Apache Superset Offering Is Now GA
The interesting thing about this story is that "batterygate"[1] represents a period from January 2017 (when Apple added the throttling behavior in iOS 10.2.1, in response to bad press about old batteries causing shutdowns) to March 2018 (when Apple added the messaging explaining the throttling in iOS 11.3, and letting you opt-out of it). I'd speculate that the HN crowd skews towards being the type who'd buy new phones pseudo-regularly, so we're probably less likely than the average person to have actually experienced the throttling on an old battery.

Despite the status quo having been the "fixed" state for 3.5 years now, that one year period has left an indelible mark on some people's perceptions of Apple, such that stories claiming performance-shenanigans will always have an audience.

And, to be fair, the messaging about an old battery is probably confusing[2]. You get a popup explaining it after your phone restarts from poor battery performance for the first time, and then it's buried in the battery-health segment of preferences. Disabling the performance-throttling is even done just as a text-link, rather than a toggle or button. There's also no call-to-action suggesting that you might be able to get the battery replaced. (That's reserved for when the overall battery capacity drops.)

[1]: https://www.ifixit.com/News/11208/batterygate-timeline

[2]: https://support.apple.com/en-us/HT208387
120W at idle on desktop computer looks not good.
That is one of the more honest admissions I seen. Like I said, I've been around long enough to have seen it occur in real time - and I regularly argued with people in the early years... I almost miss the beany baby comparisons. The majority of the time the beef seemed to be ego shielding, followed by a slightly smaller group that was just frustrated about reality not aligning to their world model. But the journalists that had declared bitcoin to be dead at some point in the past - those were the most unhinged... I'm talking life ruination levels of assmad.

Clueless people didn't start showing up in appreciable numbers until much later, well after the events of the MtGox implosion. Even then they stuck mostly to the scamcoins, because "who can afford spending $125 for one coin?!"

I don't know what you're referring to with regard to centralized control lending credibility, but I will say that fungibility is a property of currency that people generally don't seem to understand - and that you may want to consider proposed "anti-fraud" methods in that light. That was what we were talking about years ago - a currency, that was the premise. It still is, there is just a more representative cross section of the general population showing up now - unsurprisingly half of them posses a below average level of intelligence.
The thing that would bother me about this is that you only know what's being blocked; you have no idea if other spyware is getting through because your pihole just doesn't happen to know about another domain in use.

The only surefire way to block it would be to put some metal or foil around the wifi antenna (or disconnect it entirely, if possible). Otherwise the TV could connect to any random open wifi network it might find (assuming there is one in range). Even if you connect it to your own network and block all its traffic, it might just decide your network is broken and find another one.
Is there anything exciting or noteworthy in this release? My only complaint about QEMU is the networking stack feels complicated, especially for user mode networking. Maybe just need to spend more time with it.
which makes this quote all the more ominous:

"HARRIS: The risk is continuing to go down, however, as COVID rates fall, and soon this whole question will be turned on its head."

So much of this could have been predicted with some modicum of respect for evolutionary biology. It's still being ignored rather than being included as part of the decision making.
Fun the article:

"The GeekBench running score before changing the location to France is 286,632. However, after changing the location to France, the running score is 298,321."

I have a hard time caring about a 4% difference in performance.
I mean it can easily be both at the same time.
Additionally, at least Twitter has a pretty nice offline webapp that gets downloaded when you archive your account.
One should not have to, nor should they have to explain to the less technically literate ow to. The practice is disgusting and needs to be handled by regulation with teeth.
“You don’t need lidar to drive a car, so why should the car need lidar to drive the car?” -Elon Musk, like six years ago

I’m sure George Hotz also has some pithy takes on this.

Anyway, this all completely misses the point. Waymo was born of a DARPA challenge and continued to exist to search for even more DoD money. But we don’t need self driving tanks when we can pilot them remotely.
For better or worse, I do in fact get paid to do these experiments. One of my employers has this huuuge mess of MFC C++(98) code, with a lot of redundancy and repetition in the code. It's unmaintainable and we are in fact in need for better architecture.

And while much of the problem is due to historical accidents and lack of experience from some former team members, a lot of the problem I ascribe actually to MFC itself and more generally to the traditional GUI approach - Widgets in classes, code sharing using inheritance / method overriding and using other approaches as well. The main issue lies in the premature objectification (compartmentalization) of things, which prevents sharing data => it's hard to share handlers, which means there will always be a huge overhead from communication and bureaucracy and duplicated implementation efforts.

So here you have it, one example where a "feature" (OOP syntax) leads to bad choices (making up "messages" unnecessarily, using methods to implement per-message handlers), leads to an excess of "fibers" and in general of badly aligned structure in the application, and that leads to long term pain.

While with the write-from-scratch approach and mindset, there is a certain upfront cost, but an actual chance to acquire a deep understanding of the problem domain and to avoid the long term pain from ill-suited structure. In the end, to get the architecture right, the syntax doesn't matter almost at all. Once a problem is thoroughly understood and a suitable data architecture devised, computer programming is only a question of simple data copies and adds and multiplies. For example, in my code, there is basically no dynamic memory allocation, and there are no messages and no callbacks. C is a good language to program simply, it provides a lot of incentive to do so.

The issue described above is more general, it doesn't only apply to OOP syntax. Many language features are just canned solutions to do memory allocation, ownership tracking, message passing, threads organization, polymorphic dispatch... The problem is always, eventually, that one size does not fit all. And in fact, most language features seem to be optimized not for the most common situations but for small tutorial examples.

The particular code I linked above cost me 2-3 days of work (I had prior experience in the domain), which is miniscule compared to the time that is otherwise spent in a project on business logic / features.
Yeah, but that isn't even a hint of a problem. It would be like observing that Google and the mafia also both use accounting principles to organise their finances.

These large companies are going to be involved in lawsuits, no matter what. Their written communications are going to be trawled through, more than likely. Everyone in the company would have to be a bit simple for there not to be some preparations to defend against legal discovery.

Even if you believe yourself to be completely innocent of any crime, it is still stupid to make life easier for some legal assailant.
I don't know what you're referring to, but that absolutely does not describe any Chicago pizza. And while I'm sure some do, I can't think of many Chicagoans who call it "pie". At all. I dare you to go to Pequod's or Burt's Place or Labriola and tell me it isn't as good as any pizza you've had anywhere. If you think of deepdish as "soup" the you had an unfortunate experience. And Lou Malnati's buttercrust is...everything. There are astonishingly good Chicago-style hole in the walls all around Chicago. So many. But what you described...I think you're talking about something else.
Again, the article is not about throughput. How fast can you search across all historical trades?
Terra was an inspiration to create Nelua in its metaprogramming aspects. Terra's famous Brainfuck example (on the front page of Terra) is available in Nelua's examples folder for comparison of meta programming.
As an Icelander who lives in Iceland I can only say that the international press has had field day misquoting and taking out of context the program experiment here. It doesn't seem to matter now anyway as it's just used as a skeleton for other articles like this.
Perhaps, but 10 years ago you didn't have viable competitors with pure or near-pure camera based self-driving systems.
Now we have little lightly funded companies like comma producing quite compelling experiences using cheap hardware.
Not to mention tesla with near-unlimited funding, leading the way in the space.
If this goes further it's going to be frustrating to get information about public services. My local fire department has a Twitter feed where they tell the public about areas to avoid. Both local public transit systems use Twitter and it's often the best way to know about real time delays and issues (often in replies rather than main-feed tweets). It's already bad enough when these things are on Facebook, but I always appreciated when they're on Twitter and visible to everyone. It seems like now that might be changing.
I would expect the smart TV is "cheaper" for the manufacturer to make; likely they get money from Netflix (etc.) for including their apps by default on the TV, and I'm sure they get recurring revenue from selling the data they get from the spyware on the TV. I'm sure that extra money more than makes up for the cost of the extra hardware in there to make it all work.
Nice that's a pretty decent size, curious on the latency still. Thats the primary problem for a real time chat app.

Complexity of data and running business rules on it is not a data store problem though, that's a compute problem. It's highly parallelizable and compute is cheap.

For reference, my team runs transformations on about 1 PB of (uncompressed) data per day with 3 spark clusters, each with 50 nodes. We've got about 70ish PB of (compressed) data queryable. All our challenges come from storage, not compute.
Codesigning, untrusted CAs and why certain Mac apps aren’t launching
True, though I suppose we could also do without it :)
Agreed. The startup I used to work for (acquired by Intel) both before and after acquisition had a good deal of lab hardware. Between evaluation boards and rack mount hardware our server room was insanely loud - like "it's 25M away and behind a closed door, but you can still tell when the lunchtime QA and benchmarking runs kick off".

There's no way I could live with that in my house, or even a fraction of it.
Without preparing for it?
>if automation was cheap and easy then our factories would all be automated

Please describe the last factory you were in.
There is also spyware running on them. They literally spy on what you're watching and send the info home, and the data gets sold to market to you. No thanks.

Edit.

They also connect to unprotected wifi networks to send data without your permission.
Any of the photos match to the CSAM database?
Just curious, what was the rationale for choosing MongoDB?
The biggest issue for all of the self driving taxi service ideas is fleet maintenance.

First of all, you need to own and insure a fleet of rolling depreciating assets. Maybe not as much these days with the crazy used car prices, but still, you have put these cars on the books. You can't even really lease the vehicles because of all of the LIDAR and other self driving modifications that are required.

Next you have to keep these vehicles fueled - either gasoline or electricity, so you are going to need to pay people to handle that. And you have ongoing maintenance for brakes, fluids, etc. And space to park them overnight and in low demand times.

And you also have the interior maintenance. Someone has to clean up the puke and garbage and just general messiness of having humans in the backseat of this car. Throughout the day, every day.

And this has to be repeated in every single city while competing against Uber and Lyft and traditional taxi companies that already know that the driver is probably the least expensive part of this whole system.
Get an LG. Problem solved.