skysight-inc/HackerNews huggingface dataset:
> Ah but they do! As we discover those unique problems and how to solve them and how long it takes and the cost, our a priori cost estimate improves.

But it's not just our cost estimate that improves. Gen III reactors were designed with more data on how Gen I reactors were decommissioned than was available when Gen II reactors were being designed, and so on.

Finding a new decommissioning snag affects how you design the next reactor you build, but it doesn't really affect its predicted decommissioning cost because by that point you're aware of the issue and take steps to prevent it from occurring for the generation now being constructed.
Most airline websites and search engines will show you which type of aircraft a flight is on in the results. Alternatively, Google Flights or ITA Matrix can show you. You don't always get to find out easily which variant of an aircraft it is, e.g. a 757-200 vs. a 757-300 might both show as "757."
and on https://whatsmyaircraft.com/
>We can’t touch them usually.

Sure we can... with drone strikes! I'm sure dead phone spammers would have 90% support from the public. The other 10% can cry their salty tears and pretend they're getting spammed to feel better!
It used to be about the only thing you had going for you if you didn't have the political connections of wealth was the ability to become an expert through extreme effort to acquire cloistered information.

This is also certainly a contributing factor to the flatline of median incomes for 40 years in the US - among the dozen other influencers including globalism, automation, deregulation, deunionization, etc.

But we, as the labor class, are in a constant ongoing rat race to the bottom. The endgame is near total automation of production, near total availability of expertise on demand, and total capture of all resources by those own the robots. And this isn't like any other time - an able bodied man in any age before this one had intrinsic value to their community. They could be taken advantage of and thus provided for. We are going to see billions who cannot contribute meaningfully to economics. And I do not think those leading the charge towards automation are all that interested in seeing quarterlies dip to reduce suffering in the world.
The part about cause and effect was very interesting.

So possibly Facebook knows if a user is likely to buy something from a specific company and it will show an ad to them in order to boost their conversion numbers to fool the advertiser about the effectiveness of the ads. But the ad has no effect other than to artificially boost conversions. It doesn't achieve what it was paid to do; to convince users.

It reminds me of the old saying that merely finding a way to measure a trend has the side effect that it allows people to game that trend.
Show HN: Real-Time tick by tick crypto data in Node.js and without callbacks
Hi,

I've released Node.js lib that provides real-time market data feeds for top crypto exchanges.

It handles data normalization, order book reconstruction, custom trade bars (eg volume based etc), consolidates multiple feeds into one etc.
and connects directly to exchanges APIs via WebSockets, has built-in reconnection and stale connection detection logic and more.

It also uses async iteration (for await..of) instead of callbacks.

https://github.com/tardis-dev/tardis-node
There are multiple factors at work: There's ongoing maintenance as with everything, and you can probably accumulate its costs into it meaning "you're paying for a new one every 40 years through maintenance alone". Yield is going down over time (solar panels are sold with guarantees like "80% efficiency after 20 years"). And finally, technology is improving: replacing these 2006 solar panels in 2020 not only gives you back the base yield of a 2006 panel, but the base yield of a 2020 panel (see https://upload.wikimedia.org/wikipedia/commons/b/b8/CellPVef... for a research level comparison over time. That won't translate directly into industrial use though, but the direction should be evident)

So the situation is less that is "has to be rebuilt" but that it's economical to rebuild every 20-ish years (factoring in the maintenance costs: a panel that you replaced due to physical damange 10 years in needn't be scrapped just 10 years later) rather than letting the stuff hang around for arbitrarily long times.

With a proper recycling chain that shouldn't be too bad (there's little reason why the silicon can't be purified, and the doting material be refurbished), and ongoing maintenance is a concern with all types of power plant.
The 757 is similar to the 737-MAX10 except for that nasty MCAS crashing business.
Another Kinesis & custom Dvorak user (since >10 years ago) here.

I've been checking out steno, and I'm really still not sold on it as far as coding is concerned. I've mostly seen a bunch of bad demos.. (https://news.ycombinator.com/item?id=21490348)

I still think the keyboard as well as the software side of it could be improved quite a bit. I'd like to start at the keyboard, but it is surprisingly hard to get started. There are lots of custom keyboard kits out there but they all seem to be using the same standard size switches & caps that aren't what I need. So what, do I have to start by designing and making my own microswitches?! I wish I had a youtube video or three for that ;-)
>months in the lab saves hours in the library

It's possible to outperform other laboratories by accomplishing both regardless.

Working harder AND smarter has its unforseen advantages.
This is pretty cool. But I think an implementation that avoids the mutexes (mutices?) when allocating the backends and uses channels instead would probably perform better.

2 channels needed, 1 for available backends and 1 for broken ones.

On incoming request, the front end selects an available backend from channel 1. On completion, the backend itself puts itself either back onto channel 1 on success, or channel 2 on error.

Channel 2 is periodically drained to test the previously failed backends to see if they're ready to go back onto channel 1.
Theire should be after accident reclassifications to new planes.
I’m assuming it was a reference to merging in source control. A lot of “noise” in diffs, and by extension in merges and the sometimes awkward job of resolving merge conflicts, comes from little details like whitespace and punctuation rather than substantial semantic changes in the code. Many a coding standard, and even a language change from time to time, has been made with this in mind, sometimes to the point of putting punctuation in odd places or avoiding aligning items using extra whitespace just to minimise the number and/or size of diffs to check.
It's worth noting that gcc and llvm treat C integer overflow as a can't-happen condition (unless you supply an explicit compiler flag to change overflow semantics).
Me and my friend are fixing, renovating old bikes as a hobby. A rule of thumb is that each repair requires watching 2-3 youtube videos first.

We are joking that people no longer are flying to the Moon because NASA have lost all of the videos of how to assemble a rocket. ;-)
"Download" is literally the eighth word on the page, and fourth word on the navigation bar. If a person can't see that, they're destined for a Darwin award.
I think the formula is a bit different for software tutorials as they can all easily look very similar (since they are basically showing the same thing.)

Recently I have been watching a lot of blender tutorials and some people are much better than others at getting to the point and describing important details about what they are doing without losing the flow.

If the first30 seconds of the video consist of the person clicking seemingly randomly around in their UI while talking about what they are going to be talking about then I usually just stop watching and move onto something else.
Must have VSCode extensions for Front end developers
Non-mobile: https://en.wikipedia.org/wiki/Davy_Crockett_(nuclear_device)
You don't record each "waves" (nor is it even possible), you record the final result of all the waves superposed together, just like how your ears work.
So....they were slow, but smaller amounts of code was involved? That's not the same as being fast.
I’ve only learned about this through my engineering studies, so I can only really recommend textbooks. I found Proakis’ Digital Communication quite good, but it doesn’t go very deep.

I don’t know of any online resources – but I’d love to have the time to write some signal processing for communication is fascinating and has a wide impact on everyday life.

Also wrt. implementations: I think GNU Radio might be a good place to look, but honestly the actual implementation of these algorithms is often very simple, it is the theory behind them that gets hairy.
I never understand such remarcs

> Given the power requirements per card, a back of the envelope estimate put the amount of energy used to train this model at over 3X the yearly energy consumption of the average American.

So what? Training model is the hardest part, then you just reuse results

> First, it hinders democratization. If we believe in a world where millions of engineers are going to use deep learning to make every application and device better, we won’t get there with massive models that take large amounts of time and money to train.

So what? I can't run weather simulation on my laptop.
Looks like Windows will soon be launching a way for Rust to call into their COM UI API platform.

https://kennykerr.ca/2019/11/05/rust/
Keeping Warm with Starlight
> I think that means insisting on civility in our gatherings.

That's tone policing and a CoC violation. Marginalized groups have the right to be incivil.
GitHub link: https://github.com/tardis-dev/tardis-node
I'll definitely put a few of these on during my down time, you probably got yourself at least one new subscriber here!
Can this be used to install applications that require admin access, when you don't have admin access (eg. Corporate devices)?
Yep that's the clause. The clause itself is not that problematic for Tesla. What's problematic is that it can be changed over time, and it'd be foolish to single-source something as important as deep learning compute without the option to go elsewhere. Not to mention the rather extravagant Cloud pricing. So Tesla is taking a page out of Steve Jobs' playbook and it will control its own core tech. That's smart, especially considering that they already have bits and pieces of the IP that they'll need.
For sandboxing in general? There's seccomp, which uses BPF to control what processes are allowed to do.
Similarly for math: When learning calc, websites from universities that were written in basic HTML with some latex/examples or on some pdf were far better than anything else. There are also some good YT videos where they do the problems which were good as well.

Quality significantly diminishes the moment you use your face in the video (because it's completely unnecessary when explaining how to do some series testing in calc for example)
Or you could just install F-Droid.

I agree that most people probably need Google Play because the apps they use aren't available anywhere else.

But then again most people probably don't have the skills to install LineageOS to begin with.
Self-hosted multi-domain multi-tenant Support Desk, FAQ and Knowledgebase Script
Connection was slow, pages were (relatively) fast. Not hard to understand.
Web pages will never run persistent background tasks on iOS unless you install them. And even then, native apps are also both highly restricted and often have background tasks that you wouldn’t approve of if you knew what they were.
May 2019 update of Windows 10 includes Microsoft's version of Sandbox [1]. Requires pro or enterprise version. This is based on the Hyper-V virtualization.

They also have "Defender application guard" [2] which allows launching websites to Edge running in Sandbox. There should be extensions available for also Firefox and Chrome for launching the sandboxed browser, but the browser running in the sandbox is anyways Edge.

[1] https://techcommunity.microsoft.com/t5/Windows-Kernel-Intern...

[2] https://docs.microsoft.com/en-us/windows/security/threat-pro...
I'm not going to repeat all the arguments against this article as countless other HN commenters have already done a fine job of this. But it's worth making the point that this article is revealing in its use of lies, misrepresentations, flimsy arguments and circular reasoning. It all looks rather desperate.

There's so much of it going on that you have to wonder whether the author is aware of this. I.e. is this an intentionally misleading article written to green wash highly lucrative government spending on new nuclear plants? Without this spending no nuclear plants get built. Just a theory but this article looks a lot like it is written with this kind of agenda in mind.
I really don't get this fetish for lots of tiny files and nested directories, which seems to be a recent trend;

I suspect it is the same kind of thinking that says all functions should be very small (without reference to whether each function provides a single meaningful behaviour). Locally, this keeps things relatively simple, but it ignores the global issue that now there are potentially many more connections to follow around and everything becomes less cohesive. As far as I’m aware, such research as we have available on this still tends to show worse results (in particular, higher bug frequencies) in very short and very long functions, but that doesn’t stop a lot of people from making an intuitive argument for keeping individual elements very small.

A similar issue comes up once again in designing APIs: do you go for minimal but complete, or do you also provide extra help in common cases even if it is technically redundant? The former is “cleaner”, but in practice the latter is often easier to use for those writing a client for that API. Smaller isn’t automatically better.
Lion Air Flight 610 and Ethiopia Airlines Flight 302 were caused by the FAAs failure to adequately regulate the safety of the airplane type.
Is it as easy to use and as polished as Sandboxie? Or is it more low-level?
Apple Card issuer investigated after claims of sexist credit checks
>They calculate what Germany has payed in the past decades, including the very early phase of solar+wind development

Yeah, while also ignoring the untold Billions in subsidies from the early stages of nuclear power. It's rather hypocritical.
Air Force Research Laboratory looks to beam solar energy from space
Nine-year-old boy holds a bachelor's degree at the Technical University
Quick meta question.

Does this kind of article/content works for getting consultanting clients?

I am not sure I would pick them if I ever need a rust project done, but maybe I am not the target audience.
It's designed to be granular and programmable, so it's probably too low-level if you're looking for something like Sandboxie. I wonder if someone has published a set of rules that "just work", though…
Thanks, that makes sense. So now the question is - how did Sam become a YC/Angel investor from someone who taught a class at Stanford? I think we need an interview with Sam.
>Also, I'm really curious whether the custom hardware in the cars is benefiting them at all yet. Every feature they've released so far works fine on the previous generation hardware with 1/10 the compute power.

The latest OTA finally brings a hardware v3 only feature, traffic cone visualization, and traffic cone automatic lane change.
That clause doesn't apply at all though. It's not even for the same product.

As for single-source, the models are written in PyTorch, not TPU machine code, and they're pretty standard models anyway (e.g. Resnet-50). They can easily transfer to other hardware if necessary. There's not a ton of lock-in there. It doesn't justify the massive costs of ASIC development just to avoid this nonexistent lock-in and imaginary TOS clause.
Show HN: A Robotic Process Automation (RPA) Studio for Mac
Code changes are adding or correcting behavior. A lot of coding practices tend to help two things: reading comprehension and keeping developers from bumping into each other. Adding code to the same areas and then having to handle merge conflicts without introducing regressions. It’s much simpler to segregate the code into separate concerns so that new features do not intersect.

But too much decomposition also hurts reading comprehension. So if the specter of merge conflicts went away you’re left with readability, which will settle out to somewhere between the extremes of decomposition. I’m suggesting that would result in somewhat larger methods. Especially where crosscutting concerns intersect each other.
And as someone with an accent on a letter of my name, what I find amazing of your example is that the apostrophe and é are part of ascii.

No technical limitation on the computer if it supports ascii. It’s bad programming and assumptions.
>Nothing crazy about it. TPU-like stuff is ~10x the energy efficiency of GPUs and several times the speed. When you're spending megawatt-hours and days to train a single model, it adds up in both real and opportunity costs.

could you share the stats on this? Google told me to use a K-80 for training.
I'm in the UK. I get about 2-3 a week on the landline, 1-2 a week on the mobile. 30% "This is Microsoft/your ISP, your computer is hacked", 30% "You were involved in an accident that wasn't your fault", 10% oven cleaning services.
I suspect that English speaking scammer call centres are a reason for this.
Please tell us your anecdote, or are you just trolling?

Unfounded/hypothetical gatekeeping is just not required.

Its perfectly valid for people to ask if anyone has seen any evidence to the contrary of their personal experience.
How does your code structure help you against these situations:

- Version control conflicts: if developers are editing the same files all the time, there will be more conflicts and therefore more tasks related to resolve them, such as merging, re-testing, fixing bugs related to a bad merge, re-attempting the merge, etc.

- Code so complicated that becomes easy to misunderstand, and a source of an unusually large amount of bugs.

- Code so complicated that cannot be reliably tested without spending an unreasonable amount of time or relying on opaque testing methods.

- Code so complicated that increases the dependency on specific team members, usually the authors, so that the team cannot function optimally if they're unavailable or unwilling to collaborate.

- Code so complex that is impossible for an engineer to determine if the system is in a healthy state, diagnose a problem, obtain a reproduction step from a bug report...

- Code so poorly organized that developers fail to find implementations for a particular problem, causing them to implement the same thing again.

- Having multiple variations of the same code, so when a bug is found you may have to refactor multiple versions of the same code to fix the problem, if you manage to find them all.

And the list goes on and on. And a solution to these problems can have to do with how code is structured, and conventions/good practices.

If I see a piece of code that needs to know about 40 classes and 50 methods to produce a result, I know that it is likely going to be a pain to maintain. It's not subjective.

If I see a function with 1000 lines of code and a cyclomatic complexity of 500, I know that it may take at least 500 test cases to test it and will be a pain to maintain in a way that doesn't break. That is not subjective.
Then why is it listed in the grandparent as a product?
I don't agree, as I don't particularly value/want a future with self-driving vehicles.

I also think the way Tesla is going about this is utterly idiotic and reckless. It upsets me that I'm sharing roads with vehicles having these dysfunctional immature systems.

Point this crap at video game engines and don't let it anywhere near real people until it can drive millions of virtual miles in something like GTA without hitting anyone/anything and without behaving like a drunk driver who lost their glasses.
It’s great news that the source is being released, but I get the impression this essentially means the company will end active development and put the onus on the OS community for future updates.
If you validate ‘has a tld‘ or uses an external DNS server, you just have to be careful your software is never deployed on an intranet.
> Just the fact that we are discussing about an unhealthy diet, that killed millions of people in poor countries

I believe the reason these people died was lack of food in general, not veganism.
History’s message about regulating AI
Since that is criminal (rather than civil) wouldn't they have to convince the DA/Prosecutor to try the case, which seems unlikely in practice.
Show HN: Simple Automated Testimonials
New York investigates claims of sexism in Apple Card credit limits
OpenWrt 18.06.5 Stable
OpenWrt 18.06.5 released
https://github.com/openwrt/openwrt/releases/tag/v18.06.5
Downloads
http://downloads.openwrt.org/releases/18.06.5/
Changelog
https://openwrt.org/releases/18.06/changelog-18.06.5
Happy flashing the OpenWrt team.
Is sugar really bad for you? (2018)
Same here. I know / worked with several engineers involved in the development of the Flight Controls of recent Airbus airliners and that often swore that they were going to avoid taking the model they were currently working on (usually based on some "critical" technical concern that turned out to be insignificant a few weeks later).

My answer was usually to mock them and say "so just because you are looking from too close and have lost perspective you prefer to fly an ageing aircraft or trust some random Boeing contractor more than yourself".

And fast forward ten years, the "deathtraps" they were working on - A340, A380 and A350 - turned out to be extremely safe (with fatality-free records).
The development of perspective in art, the discovery of the New World, the decipherment of Akkadian cuneiform, the re-construction of the Proto-Indic European language, the Lurianic interpretation of the Zohar, the development of the documentary hypothesis.
> Did they want the extra 10% buffer for any particular reason?

They said they just were more comfortable with more margin. The stress group was an independent organization to avoid conflicts of interest with the design group. Our job was to design, their job was to verify. If parts broke, they got the black eye. If the airplane was overweight, design got the black eye. We both had to agree, and it was a system that worked well.

Most design engineers didn't work out the stresses themselves, they just hoped to pass the stress group. It was pass/fail for them. In my not so humble opinion, they were making overweight parts. I was interested in using math to sculpt perfect parts :-)

For example, the inside diameter of the jackscrew was specified to the ten-thousandth of an inch, something like 2.1834..2.2096. So I'd get the "why not make it a nice round 2.19..2.20?" I'd reply because if it came in at 2.205, it would get rejected, even though it was perfectly usable. And I got my way, because the jackscrew forging was a very, very expensive part and rejecting a usable part did not make anyone happy.

(Rejected expensive parts often got bounced back to engineering to find a way to salvage them. I just was doing the math in advance so they wouldn't have to.)
If you don't need a GUI then you can use Docker for basic sandboxing. It isn't a foolproof solution, but it's about as close as you are going to get without full virtualization.