skysight-inc/HackerNews huggingface dataset:
The link is to a PR piece from a right-wing lobbyist. The actual bill is here.[1] It's mostly about federal preemption. NHTSA can set standards, and states can't. There are also some irrelevant giveaways regarding exemption from bumper and crashworthyness standards for low-volume vehicles.

The preemption part will allow companies to test self-driving heavy trucks in California, something California DMV does not currently allow. Also, currently the California DMV can revoke the vehicle licenses of a self-driving car manufacturer if they do bad stuff, which DMV did to Uber. DMV can probably still do that.

Some of the safety standards are explicitly weak. "The Secretary may not condition deployment or testing of highly automated vehicles on review of safety assessment certifications." But NHTSA still gets to set standards, and they can order recalls.

There's not much about liability; this doesn't change who's responsible for accidents or for vehicle defects. The requirements on manufacturers are mostly toothless - "submit a plan" comes up regularly. There are no privacy standards, so Tesla can watch you in your car as long as they admit somewhere that they do that.

Can DMV still make manufacturers submit crash reports and disconnect reports? Not clear. The bill text is IN GENERAL.—Nothing in this subsection may be construed to prohibit a State or a political subdivision of a State from maintaining, enforcing, prescribing, or continuing in effect any law or regulation regarding registration, licensing, driving education and training, insurance, law enforcement, crash investigations, safety and emissions inspections, congestion management of vehicles on the street within a State or political subdivision of a State, or traffic unless the law or regulation is an unreasonable restriction on the design, construction, or performance of highly automated vehicles, automated driving systems, or components of automated driving systems. Now manufacturers get to litigate "unreasonable restriction". (Some self-driving car companies hate those reports, because they show their technology sucks. Google/Waymo is fine with it. Latest accident report: Uber vehicle just taken out of auto mode was rear-ended while stopped.)

(The biggest lesson we have so far from self-driving car accidents is that the non-self-driving cars need basic automatic braking to prevent low-speed rear-ending the self-driving cars. Google/Waymo cars keep getting rear-ended when they detect they're entering an intersection with blocked lines of sight. They'll advance a bit into the intersection, detect cross traffic, and stop. The human-driven car behind them then sometimes hits them, at very slow speed.)

[1] https://www.congress.gov/bill/115th-congress/house-bill/3388...
As long as they stay away from the lambdas and FP trainwrecks that was 8.
I've had so many ergo problems. Here's some things I'd suggest:

1. Try different mice, as people suggested

2. Watch the height of your desk. Is your desk too high? Is your wrist kinked? I love my sit stand desk for this, sometimes just moving the surface up or down half an inch makes a huge difference. Keep it moving over time so you don't get locked in.

3. Wrist exercises, both stretching and grip strength. Get a pair of grippers from amazon (https://www.amazon.com/Captains-Crush-Hand-Gripper-Point/dp/...)

Working on strengthening your forearm might help as well.
House unanimously approves sweeping self-driving car measure
Deep learning: Technical introduction
And park closer together. I imagine my office parking lot's physical capacity would increase by at least 60% if we didn't have to get in and out of the vehicles. It already has capacity for around 1000 workers (maybe more).

Even if they didn't move the lot, my car could drop me off at the entrance and then go find an available spot. The lot is huge, close to a 1/4 mile walk from the furthest available space to my entrance. I wouldn't mind not having to worry about that on those days I'm running late.
" what skilled, talented developers want to stake their careers working on software used only by a community that is in a multi-decade crisis?"

What multi-decade crisis are you talking about? Not everyone is hipster afraid to learn abstractions or unable to comprehend them. There is learning curve to J2EE and especially early versions were hard to learn, but willingness or ability to learn is not exactly mark of no-talented developer. Low skilled untalented developers go for easy to learn technologies.

Integration projects are difficult for many reasons, technology choice is not one of them.
What stands out to me is the call-out against "Data miners". This is ironic to me in that twitter has been historically one of the LEAST friendly platforms for data ingestion. They have very strict limits on # of historical tweets fetched, firehose access (to summarize, "no you can't have it"), and utilization of data, to the point that in most discussions about the platform they're seen as very closed. (or at least too risky to rely on) The author even acknowledges this in his having to use a third party service to extract the tweets to a _more searchable_ subdomain?

I guess what this ramble is meaning to say: Where does the author's globbing-in of "Data miners" come from, why the distaste, and how does mastadon solve the issue?
>Why own your own car?

Where else are we going to live?
Or a kit that isn't attached to your real identity (fairly easy to do with 23andMe, they don't require ID verification).
> Bitcoin and other crypto require a well functioning internet infrastructure, otherwise it's just data on a hard-drive.

Amazingly, not really. Bitcoin is a currency that's built to be disaster-proof, including world-ending scenarios like nuclear war between superpowers. You really just need 3 things:

1. A computer that can validate the chain.

2. The longest chain. This can be given to you via usb stick if the Internet is down.

3. Some way to send and receive blocks and transactions as the network continues building the longest chain.

A lot of work has gone into being able to achieve number 3 without full internet infrastructure. The example of a satellite beaming blocks to the world has already been brought up (though this is receive only, not send-capable for most people). However, people have also written software that can transmit blocks over HAM radio. You can't download the full blockchain over HAM relay, but you can relay blocks and transactions in real time, because the whole network is bottlenecked to about 2 MB per 10 minutes.

If you have wifi routers, you can set up point-to-point relay and broadcast systems as well. A point-to-point system can get well over 100 miles per hop. If the Interent were to suddenly fail, it may take a few weeks to connect everything together, but you could get Bitcoin up and running long before you could get anything like email working again.

> There are states (even large ISPs) that can do that.

While there are states that can split you from the main Internet, all you need is one relay that the state can't control to keep the Bitcoin network connected. It's not like a website where people have to keep asking a central server for data - once one person has relayed a block into an isolated network, the whole isolated network has that block. You can't keep the network isolated unless it's perfectly isolated, and on the scale of a country you are of course going to have people listening to the satellite broadcasts, setting up wifi relay points, or maybe even doing something less sophisticated like usb-smuggling which means it effectively takes a few days to be certain that a transaction has been confirmed by the broader network.

----------

TL;DR: Bitcoin is far more resilient than you give it credit, and it can survive the Internet going down. As long as you still have an ad-hoc way to transmit blocks to major areas, you can keep everyone fully in consensus. The infrastructure requirements of Bitcoin are far less than that of email, sms, or traditional website based, centralized infrastructure.
> The question is, who is giving the money to the banks that allows them to take this kind of a loss? People who have credit card debt???

The money comes from the business. The credit card company simply removes the money from the businesses bank account. This is one of the reasons it is so effective. Sometimes even mentioning the word "chargeback" when dealing with customer service will work wonders.
Slow releases weren't the only problem. Sometimes they even promised things that one year into development would be candidly postponed of other two years. I can't recall of any project being managed as poorly.
It all comes back to the "worse is better" thing. Frequently enough the technologies in mainstream usage are not the best, technically speaking. Mainstream programming languages are still playing catch up on the features that the Lisp family of languages has had for decades. UNIX succeeded not because it was the best OS of the time (it wasn't, MIT made much better systems) but it had a killer feature: it ran on commodity hardware, the PDP-11.
Log compaction is generally what you want, which will preserve the most recent message for every key in a topic. Event streams expanding boundlessly is something very few will ever need or want, so you'll toss messages into an "event" topic of some kind, apply the event to the most recent entry in the "model" topic and store a new version (which will be kept after log compaction, the original messages can be pruned after you need to free up storage).
For what it's worth, I've known sysadmins who strip their boxes to the bones and take pains to ensure that the "rm" command won't be able to be accidentally invoked, primarily by ensuring it doesn't exist on the box. They carry their utilities from box to box, and take them with them when they leave.

That said, any slightly-sane permission or access control scheme, including the defaults mandated by almost all RDBMS distributions (which want a system user dedicated to their use), would make it rather difficult to rm the database folder. Just opening a shell to a RDBMS's underlying server should be a rare event in itself, to say nothing of actually elevating to root, or running a sloppy/careless rm command that is uncaught by the numerous potential failsafes that sysadmins have been installing for decades now (constraining superuser access to a pre-defined set of commands, for example).

Again, the point is not that RDBMS systems are invincible. It's just that they're much sturdier, and actually designed to serve this purpose.

In what universe is "Well, hack out the dangerous parts" a reasonable answer? Talk about reckless disregard for data integrity! Do you really want to use Kafka that bad that you'd develop, maintain, and thoroughly test a custom patchset that circumvents its eviction routines, rather than just using the systems that already excel at not deleting stuff?

Secondly, eviction is a core part of a message queue's design, on purpose. It's actually a needed thing, and while I'm not a Kafka dev, I seriously doubt that it's so simple that a single flag can be disabled and we can move on.
This is probably going to be great, but I just tested out voice generation with the bare minimum of 30 recordings, and it really fell flat. When I tried playback with an input, all it could produce was a high-pitched buzzing sound and then maybe 1/4 of the words I typed in, which sounded nothing like me.

Perhaps you should increase the minimum from 30 recordings to 100?
The only vulnerability that would fit this description would be a password that would allow someone access to a system. But a password once leaked could easily be changed.
Fleet owners will send as many cars as they need into the fullest places, and as many cars as need into the emptier ones. Uber drivers are each one out for themselves, so they can't do any global optimization.
A bot that creates compilation videos from Reddit gifs
In 1983 a girl in an esoteric dress stood in the rain outside the window of an appartment of a man named Why Do All TNY Articles Start Like This.
Mesosphere adds Kubernetes support to its data center operating system
If nothing else, it is cheating and unfair to people who are respecting the law. Imagine it isn't finding a loophole where you can pay to get your dog in a restaurant, but a loophole where you can pay to get your child into a better school. Society works better when we all follow the same rules.
> It would be nice if someone make a docker image with all the tuning set (except the hardware)

This degree of optimization is something that really depends on a specific use case and the precise configuration of the entire hardware+software stack, and not a general-purpose best practices list that can be put into a container.

The author says as much at the top in the disclaimer:

> Please do not cargo-cult them. For the sake of the scientific method, apply them one-by-one, measure their effect, and decide wether they are indeed useful in your environment.

Better to take away the profiling and optimization methodologies from the article rather than specific settings.
McDonald's: you can sneer, but it's glue that holds communities together (2016)
To be frank most of my experience with concurrency (rather than parallelism) is from formal theory taught during my masters studies. But I was rusty, so I was unsure if I remembered incorrectly.
Will there be a lot fewer cars, though? Assuming you want to achieve the same throughput, you'd still need about as many cars as there are at rush hour today.
Sure, it's early. I know it and knew it when I signed up. I was not shocked to find out that the markers they'd identified as being associated with schizophrenia aren't a complete picture or a way to detect schizophrenia. And, I also know that genes aren't the only thing that determines whether one will suffer from schizophrenia or pancreatic cancer or most other diseases (as far as we know). I think they always presented the information without being misleading (though the government disagreed).

But, I also know that genetic markers for some diseases are a real thing and they are useful predictors of disease in some cases. And, the number of markers that have predictive applications are increasing all the time, as research gets done.

I don't expect 23andme to replace a doctor or a psychologist. But, I took a little bit of comfort in seeing that the markers that are thought to be predictive (even if mildly so) aren't present in my genes. I don't think they ever presented them as being a way to diagnose any condition. It was always just a fun thing you can do with your own genetic data, and maybe help move research in the field forward by answering questionnaires now and then.

I enjoyed playing with 23andme when it was focused on health-related data, less so now that it's focused on ancestry. I haven't logged in for well over a year.

I mean, I was amused to debunk my family's native American myth (which I think many American families have, for some reason), and I was also able to rule out my theory that the broad noses and dark skin that run in my family came from black folks somewhere in the family tree (that surprised me, I actually expected we had some African lineage, despite no one ever mentioning it...I assumed that's why some old folks in the family claimed native ancestry, to explain away those features). So, I guess the ancestry thing is reasonably amusing, too, but I probably wouldn't have signed up just for that, since I've always known I'm an American mutt of poor white trash lineage.
>It would be nice if someone make a docker image with all the tuning set (except the hardware)

Have you not read the article?

>In this post we’ll be discussing lots of ways to tune web servers and proxies. Please do not cargo-cult them. For the sake of the scientific method, apply them one-by-one, measure their effect, and decide whether they are indeed useful in your environment.
I'd double check your performance assumptions. Polymer-based sites are usually at the top of the list for perf shootouts, even though they tend to be purely runtime rendered. The key is only executing very little JavaScript and very carefully managing DOM creation.

The ShadyDOM/ShadyCSS Shadow DOM shims are quite fast, and the benefit is that you don't need them when you have native Shadow DOM, vs a compile-time solution that you're likely married to and is proprietary. Shadow DOM gets faster automatically as browsers adopt standards, and portable and lasting knowledge is worth a lot.

Safari's Shadow DOM implementation has improved a ton over the last year. Polymer 2.0 defaults to using it over the polyfills. caniuse.com needs to be updated - the second bug listed is fixed now.
I have tried all free js ides and some paid. VS Code was the best and is free.
It looks interesting. Would be great if you had the option to upload raw 23andme data rather than just connecting to the account, as some people probably have concerns with giving up their identity along with the information.
Because otherwise everything up to this point would've been pointless do we really need an article explaining why the survival of our species is important?
" in the modern day it's closed source code riddled with spyware and engine firmware that cheats emissions tests."

Yeah well, so the problem to me is not really missing regulations, but missing the will to use open-source.

And that is what I meant, that most people have no idea about technology.

To them it does not matter if something is open-source or not as they do not know the difference - they understand neither, it is all dark magic to them.

And of course, not everybody needs to have studied IT like we did. But I also do not understand the Linux kernel - yet I trust it. Because it is open-source and I can get in touch with the people developing it and see how it is done.

So I trust them.

And ordinary people could at least understand the same: if something is developed in the open, then other people have the chance to check it. If it is closed - much harder.
Very simple. And I have no doubt, that this knowledge will get in the heads of the people. It just takes some time (and action of course) - Computers for everyone is a quite new thing ...
They are there because they are used to think that way. It's conways law written all over it... There's no actual reason for them to do it. They replaced their paperwork with a system that does the same thing. Fraudulent transactions can you find without the need of summarizing it.

Yes you can do DDD/CQRS without ES but CQRS is not needed, it's just a technical construct not solving any verifiable problem. DDD on the other hand is more sane and to some extend, verifiable.
What open source JS Engines existed at the time Roku launched in 2002?
or on windows just
%0|%0
The case for a Category 6 rating for super-hurricanes like Irma
Sun Unleashes Monster Solar Flare, Strongest in a Decade
The Most Successful Google Internal Teams Shared These 5 Traits
You are being a snob. There's no degree requirement to be called a data scientist. Even if there were, why would you exclude a B.S. or an M.S.? It's not like they're calling themselves a Doctor.

You'd be stupid to market yourself as a data specialist when every startup is looking for a data scientist.
Waze Rider and Scoop are actually pretty great for matching people up for carpools (and are specifically for that purpose and that purpose only, unlike Uber Pool/Lyft Line), and yet I don't see a large number of people using either service.

I suspect people with cars are still very protective of their ability to completely control their schedule; agreeing to ride in someone else's car makes it difficult to run errands after work without first stopping at home to pick up the car, for example. And what if they have a ride scheduled for 5pm but find out at 3pm that they need to stay later? With enough scale it shouldn't be hard to find an alternate ride, but we're not to the point where people can expect that to be easy.

I think people could definitely rearrange their lives a bit to make this better, like planning to run errands on weekends, or close to home (instead of work). Or setting reasonable boundaries with their employer (I'm scheduled to leave at 5pm, and not a minute after -- unless you want to pick up the tab for a taxi). But people are selfish, and stuck in their ways, and would, for some reason, prefer to sit in traffic.
How much math do you really need to know for a career in Data Science?
Thing is, as long as there is one honest person with a connection to both networks, they can easily serve as a relay between them, and keep both networks fully synchronized.

If an attacker is on both networks and trying to double-spend, it's extremely likely that someone honest is also on both networks who is successfully keeping the two networks fully synchronized. In this type of situation, you can make yourself safe just by waiting for 4-6 confirmations instead of the usual 0-2 confirmations.
I'm 30 and a senior developer. But I started out with an English degree and had planned to be an academic. In the intervening years I have been a technical writer, a business analyst, a QA and even had a ill-judged stint as a recruiter. Oh, and I was a UX designer for a year, albeit not a very good one.

Now I am thinking of becoming a lawyer or civil servant, but worry that I may no longer be mentally agile enough to learn a new skillset. So I'm very glad to read this article!

Incidentally, as someone heading the opposite way to yourself, do you have any advice / warnings for a developer thinking about law?
I wonder how it would work using training data from one language in generating voice in another language.
There's very few situations where a car wouldn't be legal to drive in another state. For one, states are generally expected to respect other state's certification and licensing. Additionally, short of the hallmark "cars which have no steering wheels", which likely just won't work outside their programmed area anyways, you could just drive the car normally when in a state which doesn't support it.
> You may approach this as #homepage .callout at first but it begins to become hard to manage when you realize you need to refactor it into a side wide style.

So one approach would be to have a "callout" css file, nest everything under ".callout" and have several callout styles you can use inside that file (e.g. ".callout .warning")?

> Generally I approach everything in attempts to make it re-usable. And organize what I can into components

Personally, I find very little CSS can be reused between different projects as designers want completely different looks so I let things like Bootstrap take care of the basics and customise from there. It takes time and effort to make things reusable (same with code) so you need to weigh up how likely you are to actually reuse things and how much time that would save you.

Sometimes duplication between projects saves time compared to maintaining the code for some generic widget that has to work in many scenarios. For me, I don't think it would save much time as each component is usually small and simple but I could understand if you were to create e.g. a calendar widget where it involves a lot of complex styling and code.
Why is it all or nothing? The other poster already brought up Germany, it isn't all or nothing there and they seem fine.
wow.
This is the kind of article i'm expecting to see when I google for "Nginx best practices 2018".
I am so far behind, maybe 20% of my usual setup include those recommendations.
Thank you Dropbox.

If someone can point me to a thorough article like this on the lua module, I will thank her/him forever.
Consumer vs business computers is one of my favorite topics. Even with Lenovo, Superfish is not the only example.
There's always been a love-hate relationship between England and France. Some Englishmen are Gallophiles, others avovedly not. Note: this is about French culture, its literature and way of life, of which French language is a part, not French language itself.