skysight-inc/HackerNews huggingface dataset:
Wow, Tesla instantly went from my dream car (having replaced Bentley) to Do Not Buy. I simply will not buy a car or other dangerous equipment from a company that doesn’t care if I die and only cares about their brand.
As far as tooling, sure. But this will take it up a level to base language. Surely that's an exponential difference?

Frontend dev won't mean what it means today.
Hope some of the entry/mid level security cam vendors are working on this type of detection as motion detection currently leads to so many false positives once you want notifications.
> Basic memory management and error handling, for example, are radically easier and less error prone in C++ than in C.

Microkernels don't need memory management. Dynamic memory management in a kernel is a denial of service attack vector. Fuschia is built on a microkernel, so I expect they will follow the property of every microkernel since the mid 90s: no dynamic memory allocation in the kernel, all memory needed is allocated at boot.

Furthermore, you don't want exceptions in kernel code. That carries huge and surprising runtime execution and space costs.

Simply put, there is no reason to choose C++ for a microkernel, and many, many reasons not to.
Tesla is a fucking computer. The dude that took his hands off is a human. One of those has actual intelligence. You don't get to blame user error on the computer because someone died.

He. Took. His. Hands. Off. The. Wheel.
Yup that's the one I have, still holding up pretty well and I guess that's why.
I feel like making a deal between game publisher and movie studio is not an easy process and creatively game publisher would like to have sign off on pretty much everything.

Negotiating split and who puts money upfront would be a nightmare.
Couldn’t it be fairly trivial to raise the salinity? We have tons of salt. Enough at least to kick the can further down the road.
> In order to "delete" my phone-shadow-profile, facebook needs to remove my phone number from their internal copies of my friend's contact lists.

This is (potentially) not viable. Your friend's contact list is not your data, it's their data (about you) and they store it on FB servers. Right now it's probably used only for ranking and friend suggestion, so what you suggest would work. But if FB would decide that say messenger should work also as contact sync app (it already allows you to send SMS to people in your contact list), this would cause that your contact could not be synced, and really break user experience, as you would be able to delete your phone number from your friend's phone books.

More philosophical question: if you should be able to do that [delete your phone number from your friend's phone book on FB], should you be able to do that also from google contact sync server? From gmail? From your friends phone? Or from your friends physical (manually written) phone book? Where to draw a line, or how to approach this?
> The GP gave real world examples of where this is an impact. I'm not sure why you are arguing against the design.

Because the design is questionable, and so the example is questionable. Isn't that obvious? Why else would I bring it up?
Tư vấn định cư Mỹ theo diện đầu tư EB5
Thắc mắc về giấy nhập cảnh để định cư Mỹ là điều mà đa số đối tác, số đông để ý hiện nay. vì cớ, để đến bất kể một đất nước nào bạn cần phải sở hữu giấy nhập cảnh thì mới có thể vào nước. tùy vào mục tiêu, nguyên do người tham gia tới dân tộc ấy mà sẽ được sở hữu cho loại visa tương ứng. Có hai loại visa chính đó là visa định cư và visa không định cư. visa không định cư thuộc về những khách hàng đến nước Mỹ như: ngắm cảnh, gặp người thân thuộc, sinh viên đến giao thiệp và lưu đổi văn hóa, đi làm việc ngắn hạn,… còn những visa lưu trú được phép người tham gia được sinh sống và làm việc ở Mỹ giống như một người Mỹ bản xứ thật đúng luật của Chính Phủ Hoa Kỳ. Riêng với việc xin visa ở Mỹ, ngoài ra đáp ứng được các quy định và tiêu chí về quy tắc của Chính phủ Mỹ, người tham gia sẽ có được giấy chứng nhận được gọi là là thường trú nhân Mỹ tùy thuộc dạng mà bạn xin phê duyệt. Sau một thời gian, nếu cung cấp hoàn tất quy tắc người tham gia còn có thời cơ được nhập quốc tịch Mỹ.

Thông tin: http://immica.org/tin-tuc/tin-tuc-di-tru-my/nhung-dieu-can-biet-khi-chon-dich-vu-tu-van-dinh-cu-my.html

Địa chỉ:

HCM: P.905 & P.1703, Saigon Tower, 29 Lê Duẩn, Q.1

Hà Nội: Lầu 10, Pacific Place, 83B Lý Thường Kiệt, Q. Hoàn Kiếm

Đà Nẵng: Tầng 3 - Indochina Riverside, 74 Bạch Đằng, Hải Châu

Phone: +848 38274888

Email: Vietnam@immica.org
Except... he actually wrote it. It’s like if someone said Dropbox is a weekend project and then it was available for download the next Monday.
It won't take that long.

Also, people are terrible at detecting objects directly in front of them and just like computers, the human brain can be cheated, overloaded, inept or inexperienced leading to an accident.

Now we have cars with lane assist, smart breaking, auto pilot features and that's only in the past 5-10 years.

Of all the places where technology can save lives, its definitely in vehicles/transportation.
Joking, right? If not, I’ll match your talent for understatement with my own: the ocean is very big.
> You've clearly never tried to support more than one browser.

Please be as polite in a forum as you would be during a face to face conversation. You'd never start an office/remote work conversation with that line, would you?
>What I really need is just a huge table with two fields: “token”, “content”

Sounds more like a key value store and less like a relational database. Although you can store key value data in a relational db of course, there may be a better tool for the job.
Looks like a person who claimed (4 years ago) to know the person who did it, and has recently ruled them out per the linked Reddit thread.
The principle is very general. Colimits are the essence of gluing pieces of data together so they appear just about everywhere in mathematics in some form or another. Vector clocks do form an instance of colimits. A special kind in fact, a colimit of a partially ordered set of objects.

There is a fundamental lemma of category theory that says that you can always embed a category into a larger one that allows all colimits, i.e. gluing constructions (subject to cardinality considerations).
I think backing all the global currencies with absolutely nothing is a relatively new experiment and we have yet to see if it works out.
i tried to use zip car for a multi day rental in vancouver. i talked to people at zip car and they said that is not allowed this was 2015
I keep seeing these articles, but I think they're only debunking the craziest interpretation of learning style theory. Obviously it's not going to be perfect, and you're a fool to pigeon-hole yourself into one mode of learning. But there's too much anecdotal evidence to dismiss the whole idea. When I've raised this before, over person suggested that we view learning styles as deficiencies in particular modes of learning, rather than special abilities, which I think fits both the evidence and the overall theme of learning styles just fine.

People's brains are different, and learning is an important thing we do, so it should surprise no one when people learn differently. It should also surprise no one when those differences turn out to be complicated and hard to measure, just like our brains. So yeah, the pop psych version is over simplified, but don't throw the baby out with the bathwater.
One place I worked addresses this by having mandatory post-deploy monitoring / patch day. We’d all do a deploy and keep an ear to support / logs while going ahead and improving things we knew needed a little clean up. If we saw anything come in from the release, we fixed it immediately.

An entire day is excessive in a CD setup, but for a two week release cycle it worked well. Kept the rough edges out of customer view very well.
It's a good story and I liked their take on it, but Mass Effect borrows everything you mentioned from Babylon 5.
Great copywriting. It seems in part this is a user interface issue in that the limitations of the system are not clearly enough surfaced so people’s expectations are off-base.
> Escaping rules are well-defined

Except when they aren't? I'm thinking of things like the bash exported function bug, an obscure feature nobody thought was there turns evaluating environment variables into RCE. Not to mention different shells may do things slightly differently and you may get caught doing something unexpected.

So why not leave the shell out of the picture entirely? I think execve and friends are much easier to get right than escaping. There are still possible security bugs to consider (eg., if using the -p family such as execvp, who controls PATH? Is anything on PATH writeable?), but the shell won't be among them.
Oops, my bad :(

OK, didn't protect Noriega.
Lord that's impressive. Can I get an API?
How is "technical debt" handled in meatspace?

Don't the bean counters at Ford Motor Company (for example) nark on the assembly line workers and industrial engineers and QA/QC folks have work pile up, broken machines lying around, uncleaned trash?
Dumping large volumes of nonessential content into the Ethereum blockchain sounds like an antipattern.
It's a global variable in our code.
This is really cool!

I was able to hear the fundamental with its slider turned all the way down and the harmonics up using decent in-ear headphones
Would you mind pointing me to the implementation spec for the Pixel 2's touchscreen controller?
The only time my improvements have even been noticed is the pointy haired boss said "Well, you should have thought of that sooner. What am I paying you for?"
I agree, I find the same of myself, and I beat myself up over any loss of concentration.

The solution might be a system where the driver drives at a higher level of abstraction, but ultimately still drives.
Driving should be like declarative programming.
For example, the driver still moves the steering wheel left and right, but the car handles the turn.
Or when the driver hits the breaks, which is now more of a on/off switch, the car handles the breaking.
The role for the driver is to remain engaged, indicating their intention at every moment and for the car to work out the details.

Edit: On second thought, that might end up being worse. I can think of situations where it might become ambiguous to the driver of what they are handling and what the car is handling. Maybe autopilot is all or nothing.
There’s issue about with newlines being replaced with spaces. This is an issue in areas that use white space pre style.
Ask HN: How did you overcome the junior hurdle? (warning: rant)
Hey HN, I'm a junior developer who's been working for a startup in South Korea for about two years now. Been feeling really burnt out lately, primarily because I feel that I've plateaued in terms of learning. My day to day has gone from "create an interactive infographic" or "implement a tagging system" to mundane tasks like "add a button here" or "change this modal behavior" -- a place I don't think many developers want to be.

It's also been a while since I've started noticing terrible development practices, like:

1. Using spring boot without taking advantage of its features

2. Commits affecting multiple features, committed with no description of changes

3. Each jsp page has its own js and css (big headache as the production app is getting bigger)

4. Individual page js isn't self-invoking, meaning all variables and private functions including API callers are exposed to the client (granted, the js files are exposed anyway, but still)

5. Widespread use of anti patterns (deeply nested arrays instead of proper data structures, constant polling architecture, etc.)

6. No bug tracker, no pre-deployment testing other than sysout, console log, and "click it, does it work?"

I am forced to follow the company's coding style for obvious reasons, and I'm not in a position to suggest that we overhaul this mess. I wouldn't even know where to start.

The main problem I think is that the entire development team is junior. There are no senior developers, no software architect to guide app development, which also means no best practices and no mentors for a junior like me to learn from.

Have any of you been in a similar junior environment? How did you improve? I just feel like I've regressed in terms of good development practices since I've started working here, to the point where I'm losing sight of better ways to do things.

If you've made it this far, thanks for hearing me out. Would greatly appreciate some advice.
It seems more clear to me. Who chooses to live, eat, and sleep in a small strip mall sublet, sharing a room and one bathroom with 10+ other people of their own volition? Leaving the place almost never? What they say is less telling than how they live.
I agree, and I think the psychological effect will be stronger if the feature is called autopilot. It conveys the idea that the car can pilot itself.
Another day, another example of regulatory capture.
No.

A good boss knows to get out of the way, clear a path if necessary.

If boss can't trust the minions to do the right thing, someone's got the wrong job.
Here's a login-less one that looks like it doesn't make any network calls with the data you enter: https://networthify.com/calculator/earlyretirement
This has been done before, and it's time for it to happen again.

Hailing from 1995, Flash (nee Future Splash) was a dev tool for designers. Design, animate, optionally code, then ship to production on any device. For that connection between design and code [and the imaginativeness, the creative empowerment!] there's still a big ol' Flash-shaped hole in the world. [1]

More recently, in the game industry, Unity brought together design and code in a compelling way — by integrating existing tools. E.g. do your 3D modeling in Maya, do your coding in Visual Studio; find a common workflow to design and code together for any platform through Unity. This has worked well enough for Unity to capture > 50% market share in the game industry over the course of the last ~decade.

The key to this problem is a workflow-unifying tool that
1.) enables designers and developers to create software together through comfortable + familiar tools
2.) ships that software to every device

Like Unity. Like Flash. It's been done before.

[1] I'm passionate enough about this subject that I've dedicated my career to it. I'm on the Haiku team (YC W18) and we've taken a lot of inspiration from Flash, Unity, and modern software practices to build a cross-platform solution that allows designers and developers to create software together. https://www.haiku.ai/
Let’s say I take your assertions at face value. Supposedly qualified, intelligent engineers who were no doubt aware of these points still decided C++ was an appropriate language to implement this microkernel.

Surely there’s a reason. Why?
Yeah, but there are many ways to achieve this without the grocery store. There's nothing special about it as an irreplaceable social hub.

My point is, compared to going to the butcher and baker, who are artisans running businesses that are to some extent expressions of theirselves and maybe even their heritage, a supermarket is relatively soulless.

Save the time and do something like dance, art, or sports.
Timing in particular is tricky. On Linux, you could use the vDSO for high-resolution timing but, from an attack perspective, it’s a red herring. Any serious attacker would use RDTSC, RDPMC, threads and shared memory, or some other hardware mechanism. On x86, RDTSC and RDPMC are controllable by the scheduler (there are bits to turn them off), but it doesn’t really fit in a capability model.
Heads up: my username @twitter seems to trigger a bug, as I expected it would.
> Microkernels don't need memory management.

Of course they do. It takes memory to hold metadata about a process. It takes memory to hold resources about other services. It takes memory to pass data between them.

Just because that memory is reserved at boot doesn't mean it suddenly has no lifecycle of any kind.

> Furthermore, you don't want exceptions in kernel code.

Nobody said anything about C++ throw/catch exceptions.

> Simply put, there is no reason to choose C++ for a microkernel, and many, many reasons not to.

If you want to avoid C++ that's great, but to argue for C over it is insanity rooted in nostalgia.
It just gets kinda exhausting. If you whitelist characters you have constant maintenance, if you don't some stupid edge case slips through. You're right of course, but I sometimes get discouraged at how much work every little thing is.
Sure, and Go's most prolific users are in infrastructure software for distributed systems. You seem to agree with the quoted statement.
No, it is absolutely not. I'm not sure why you keep posting this as if it is definitive.

Let me put it very clearly for you: it is not acceptable, in any shape or manner, to expect your users to have to "save themselves" from your product killing them every 5 seconds. If your product requires that, it is a bad product.

Furthermore, your entire argument of "it's just a level 2 system..." falls apart when you consider that Tesla jumps through several marketing hoops to deceive people and make them believe it isn't just a level 2 system. When you visit Tesla's webpage on autopilot [1], the first and only thing you see at the top of the page are the following words in big, bold text:

>Full Self-Driving Hardware on All Cars

>All Tesla vehicles produced in our factory, including Model 3, have the hardware needed for full self-driving capability at a safety level substantially greater than that of a human driver.

It is not until you get to nearly the very bottom of the page that Tesla displays a disclaimer that "when we say 'full self-driving', we don't actually mean full self-driving, because that would be illegal and isn't available yet." There is only one single sentence, buried within a paragraph mid-page, that says drivers must remain alert and prepare to take over. The rest of the page is also filled with language indicating that autopilot is capable of turning itself, switching lanes itself, speeding itself up/slowing itself down, etc.

It is not unreasonable whatsoever for someone to read this webpage and assume that autopilot will magically take them whereever they need to go. This webpage is in stark contrast to the reality, where autopilot will actively steer you into a concrete barrier and kill you if you do not babysit it. And to make things worse, Tesla apparently considers this to be a "feature".

According to your Twitter, you own a Tesla, so it seems you have a little bit of fanboy-ist bias going on here. I'd suggest you take off the Tesla fanboy ballcap and consider how you would feel if this were a different product. If someone sold you a smartphone, but told you "this phone never requires charging because it has a mini nuclear reactor in it. Be careful though, because if you don't keep your eyes on the phone at all times and press the 'please don't explode and kill me' button every 5 minutes, you'll die!" would you be defending that phone in the same way you're defending Tesla?

1: https://www.tesla.com/autopilot
Per-company unions are actually very effective and can't be encouraged enough. In a well run company union, employers have no other choice for purchasing labor - functioning just like a local monopoly. AT&T charges me out the ass because I have no other option; per-company unions enjoy that same privilege. Very few people break ranks.

That said, the biggest issue for per-company monopolies is having everyone agree on a wage structure. They work easiest for similarly paid groups of people.
I meant time-delayed. Eg, run this in 10ms type of thing. How else would you do things like exponential backoff?
Big is still not infinite.

There must be some quantity of salt we can dump a year to raise salinity. We should be rigorous, and find out what that quantity is. If we can change a climate, we can change an ocean.
If, as I suspect, they'd be willing to rename ChromeOS to be "just what Android is now" (like how Mac OS9 was succeeded by NeXTStep branded as Mac OSX), then I don't see why they wouldn't also be willing to rebrand the Chrome Web Store as "what the Google Play Store is now." Of course, they'd keep the music, books, etc.; those are just associated by name, not by backend or by team.

But they wouldn't keep the current content of the Play (Software) Store. The fact that every Android store—even including Google's own—are festering pits of malware and phishing attempts, is a sore spot for Google. And, given their "automated analysis first; hiring human analysts never (or only when legally mandated)" service scaling philosophy, they can't exactly fix it with manual curation. But they would dearly love to fix it.

Resetting the Android software catalogue entirely, with a new generation of "apps" consisting of only web-apps and much-more-heavily-containerized native apps (that can no longer do nearly the number of things to the OS that old native apps can do!) allows Google to move toward a more iOS-App-Store-like level of "preventing users from hurting themselves" without much effort on their part, and without the backlash they'd receive if they did so as an end unto itself. (Contrast: the backlash when Microsoft tried that in Windows 8 with an app store containing only Metro apps.)

I expect that the user experience would be that, on Fuchsia-based devices, you'd have to either click into a "More..." link in the CWS-branded-as-Play-Store, or even turn on some setting, to get access to the "legacy" Play Store, once they deprecate it. It'd still be there—goodness knows people would still need certain abandonware things from it, and be mad if it was just gone entirely; and it'd always need to stick around to serve the devices stuck on "old Android"—but it'd be rather out-of-the-way, with the New apps (of which old Chrome Apps from the CWS would likely be considered just as "new" as newly-published Fuchsia apps upon the store's launch) made front and centre.

> Seems more likely they'll allow HTML apps into the Play Store, eventually getting rid of the Web Store entirely.

I would agree if this was Apple we were talking about (who is of a "native apps uber alles" bent) but this is Google. Google want everyone to be making web-apps rather than native apps, because Google can (with enough cleverness repurposed from Chrome's renderer) spider and analyze web-apps, in a way it can't spider and analyze native apps. Android native apps are to Google as those "home-screen HTML5 bookmark apps" are to Apple: something they wish they could take back, because it really doesn't fit their modern business model.
It may be the similarity of the medium that hamstrings Hollywood. Going from prose to a movie tends to absolutely force a lot of compromises. You no longer really have the option of extensive narration, seeing into characters' thoughts, etc, and the whole thing has to fit into 200 minutes at the outside. A video game already operates under similar constraints as a movie, so it's possible to create a movie that's very similar. You just take a recording of a well-done play-through as your outline. It could be that without the excuse provided by the drastic change in medium, Hollywood types lose the nerve to do what's necessary.
Down voters please respond -- off topic? Something else?

Genuinely interested.
I also think the foreign investor thing is overblown, but it’s always the marginal demand that causes prices to go up. Take 10% of the property owners out of a market and prices will go down.
There's dynamic memory allocation in the kernel:
https://fuchsia.googlesource.com/zircon/+/master/kernel/kern...
https://fuchsia.googlesource.com/zircon/+/master/kernel/obje...
It has always been associated with Google for as long as it has been known outside of Google. :)