skysight-inc/HackerNews huggingface dataset:
Recognizing the right tool for the job landed you job security for the next two years (and you're deserve it!)

But it could have very easily gone the other way. If your website had complicated validation rules on multi-page forms (not unheard of in healthcare) the site would be better off for some basic state management interacting with a standardized authentication/authorization framework that you didn't have to write.

From what you're describing, it sounds like you did right by the client in this circumstance. But sometimes, it does have to be complicated. And in those circumstances, frameworks and javascript (unlike garbage) have an important place.
A Unified Framework of Five Principles for AI in Society
As someone who hasn't done much web development in the last 10 years, it is mind-boggling how much you need to know in order to be a full-stack engineer these days. I tried to start a project a few months ago and just trying to decide on a technology was difficult. Npm, Gulp, Grunt, Webpack, React vs Vue vs Angular...I don't even know what half of these tools even do, why they're needed, not to mention the learning curve to get up to speed.
Multiple languages could use this ... python, ruby, php, JavaScript... could be better than using imagemagick for resizing uploaded files
I don't disagree. It is how the legal profession works, though. If clients demanded something more efficient then there would be incentive to change, but they almost never do.
There are reasons to be skeptical of this alleged quote by Ehrlichman.
As user GatorD42 pointed out when this was brought up before:

>...Baum claims Ehrlichman said that to him in 1994 while he was researching for a book he published in 1996 about the drug war. He didn't include the quote in that book, but instead published it in 2012 and again in 2016, after Ehrlichman had died (in 1999).

This is an amazing and explosive quote - if Baum had included it in his book in 1996 I am sure it would have garnered a great deal of attention. Instead Baum would not include it in his book, but instead would wait for decades later when Ehrlichman was no longer around to dispute it.

At any rate, if the quote was actually said by Ehrlichman, it doesn't actually describe the drug polices of the Nixon administration. While Nixon is remembered for "war on drugs", the actual substance of his policies seem to be different than what people think it was:

>...I have been fortunate over the years to discuss the distorted memory of Nixon's drug policies with almost all of his key advisors as well as with historians. Their consensus is that because he was dramatically expanding the U.S. treatment system (by 350% in just 18 months!) and cutting criminal penalties, he had to reassure his right wing that he hadn’t gone soft. So he laid on some of the toughest anti-drug rhetoric in history, including making a White House speech declaring a “war on drugs” and calling drugs “public enemy number one”. It worked so well as cover that many people remember that “tough” press event and forget that what Nixon did at it was introduce not a general or a cop or a preacher to be his drug policy chief but…a medical doctor (Jerry Jaffe, a sweet, bookish man who had longish hair and sideburns and often wore the Mickey Mouse tie his kids had given him).

http://www.samefacts.com/2011/06/drug-policy/who-started-the...
Thanks, that makes sense. Here’s another related question: do you need a separate LLC for every MVP-level product or can they all be rolled into one? (Along with personal consulting work perhaps?)
> Social scientists pushed to be put on the same level as natural scientists, but then they pushed a bunch of politicized bullshit and tarnished the reputation of all scientists in the public's eye.

I largely agree with this, but I think the masses on the right approach it more like the first argument:

> Social science is nut trustworthy so no science is trustworthy.

More accurately, it seems to me that it has become "social science is not trustworthy and I don't agree with the field's mainstream ideas, so I can consider any science I don't agree with to be not trustworthy". So when climate science suggests that climate change is a problem, and the proposed solutions do not agree with right-wing economics, the natural conclusion is for them to reject climate science. This conclusion has been reached by right wing governments across the world, so it certainly seems that those who follow the ideology tend to reach it.

I think it happens both ways with people of all political persuasions, saying "I agree with these conclusions so this science is trustworthy" or "I don't agree with these conclusions so this science is untrustworthy".
Repeatedly playing https://flexboxfroggy.com/ is better for developing intuition.
He's hilarious and has a column in the same style every day! Subscribe and enjoy life a little more every morning:

http://link.mail.bloombergbusiness.com/join/4wm/moneystuff-s...

(no affiliation, just a Matt Levine fan)
I don't know a single person that owns neither, and I know at least a couple dozen people with an iPhone.
Most papers in most disciplines end up not being worth much, and the incentives regarding publishing hold across all of computer science. Is there really something particularly bad going on in deep learning? Or is it just the usual process?
Here's my hot take: Instead of waiting 20s for your truly interactive site with refine-as-you-type search bar to load, which, when finally loaded, will lag so much on my mobile connection that it is just plain annoying, I will use your competitor's site which loads within 1s and has a plain old <input> field for search.

Not every site needs to be truly interactive. Not every site needs JS. Unless you're building a 3G+ or desktop-only web experience, use it responsibly.
> Web development today is easy (compared to 15 years ago) once you know this toolchain

Web development is harder for the simpler tasks that were common 15 years ago. It's harder so the harder (or impossible) tasks of yesterday, today and beyond, are easier for some values of harder and easier related to time and custom coding.
What's the point of random wiki pages on hacker news though?
It depends on the goal. If the only goal is to reduce car usage, sure. However, the area already has a problem with housing costs and a rule like this would just cause costs to skyrocket near transit hubs. You need a more robust public transit system for that type of proposal to work without those negative consequences and LA isn't there yet.
Pointing directly and solely to caloric intake when discussing obesity is the “It’s just economics 101” of the nutrition issue: technically right, but so lacking in nuance that it ceases to be interesting.
I might pick a nicer phrasing for your last point: if your team is not good at clean architecture (separation of concerns, conceptual model, etc.), microservices will “solve” that in the same way that adding gasoline solves a fire. If your team has gotten better at that, however, it might be a good strategy for migrating pieces out of an old system.
These "i hate debugging wandering pixels" and "i don't want to figure out why my css doesn't work" opinions sounds like they come from people who aren't really front end developers; like they come from the kind of dev who would sit and complain about the frontend devs on their company, thinking that they're a lower class of people.

I've been working on the server- and client-side of the web for about 10 years now, and I can't recall running into these "wandering pixel" issues they talk about in the past ~4 years.

Frontend development is not just about building a cute website for grandma anymore, and that's why it's complicated. We're passing more responsibilities to the browser, and we have to care about performance when doing work there, and that's why it's complicated. Writing performant software for an unknown machine is hard, and that's why it's complicated.
No fancy circuitry is needed. Just use one fiber. I suspect that 100BASE-T can pull this off with one pair and some hackery. RS232 should work work only one direction connected.
You guys are both right. Removing cars from a bus lane makes the buses go faster.

And having frequent stops makes buses go slower.

Traveling long distances doesn't make the bus any slower; it just limits the frequency you can revisit a stop on the route without increasing the number of buses on that route.
Indeed, that response is seemingly from twenty years ago. 90% of LA history is in downtown also. What downtown looks like today:

https://urbanize.la/post/perla-condo-tower-tops-out-4th-broa...

Still, skid row is as bad as it ever was.
Is your startup compliant for SB 1343?
Why has no-one made a tool that worked like Flash.

I get that the flash plugin sucked and was a battery hog.

But the development environment was quite decent. I'd love to be able to make HTML5 content in the same kind of way.
Technically, changing a registry key changes bytes within a large file, yes.

But in practice, the only way to change registry keys/values is by going through the registry APIs provided by Windows; I certainly wouldn't consider registry operations as file system operations.
Upwork Reports Second Quarter 2019 Financial Results
Battery-Powered Ships Next Up in Battle to Tackle Emissions
Just listening to both songs once, I didn't notice anything close.

What I'm curious about are the cases where it is extremely obvious that one song is based on another, and no one says anything.

Case in point: "Jolly Roger" by Adam and the Ants [1], from 1980. This is extremely similar to "The March of the MacGregors" by Ennio Morricone, from the 1966 film "Seven Guns for the MacGregors" [2].

It's not only the same melody, "Jolly Roger" is also largely the same arrangement.

[1] https://www.youtube.com/watch?v=hc_-vSIy3fY

[2] https://www.youtube.com/watch?v=N5JQ1JTsJ4k
Because it had to play catch up to native apps feature wise due to demand, while building upon a base that wasn't intended for that, while serving the same app to literally thousands of different environments and expecting it to work perfectly.

Thus, growing pains and overly complicated frameworks/plugins/other bits slapped together to address the core issues which ballooned the complexity. But we all knew that.

What's more impressive is that things are getting less complicated. Browser monoculture, while bad for the freedom of the web, is going to simplify things radically. Only having to target rolling releases for Firefox and Webkit? That's a dream from a cross-plat support side. Also javascript is actually pretty good now. Webcomponents once Chrome 77 drops and Firefox matches parity will finally be production worthy, and they're actually quite easy to build. I've been making static sites with them recently and it feels so much cleaner than going with a React or other component library approach that uses a vdom. The HTML is readable again, and there isn't any needed compilation step or crazy npm dependencies.

While it will never be as easy as it was back in the mosaic days, web dev is simplifying.
Questions about performance are often complicated affairs that involve considering all factors including hardware, software, data operated on, etc to get meaningful answers.

That said I don't think data exists to show that SeL4 is faster than mainstream OS kernels just much faster than research microkernels which have always been much much slower than mainstream monolithic kernels.

In fact one would reasonably suppose that it would be measurably slower due to increased overhead. This may well be well worth it but this doesn't mean we ought to engage in speculation not backed by data.
JPG vs. PNG vs. GIF vs. SVG
Modern Javascript is complicated*. Elm Lang on the other hand is great for web dev.
Used to be done with a literal diode.
Why do you believe lenders are super racist?
Where the definition of important is defined by the News, yes.
Building a Kubernetes Platform at Pinterest
In addition to what unilynx mentions about strncpy(), the size arguments are also, effectively, the remaining space in the destination buffer, not the entire space in the destination buffer.

So, you have to figure that out. It isn't hard (hell, it's trivial) but I think if you're either going to be aware of the pitfalls — and then these functions are mostly not going to help you — or you're not, in which case you're just as likely to pass the wrong value for the size (dest's size/src's size) and overflow the buffer anyways.

Honestly, if I had to do more than a trivial amount of string manipulation in C, I'd be wrapping that in a mini library to manage some sort of stronger string type or finding such a library (glib? ICU?) very quickly, depending on needs. std::string was one of the things in C++ that made me question why anyone was still using C, given how much less error-prone it is, comparatively. (std::string is not without problems / only as compared to char * in C.)
Agreed. It is clearly more complicated than "worthless lazy person can't control themselves."
That runs only the fan, I seriously doubt that Toyota micro panel can handle aircon
I recommend looking at Phoenix LiveView. It’s still early, but it’s a revelation in terms of eliminating pointless, complex JS.
Even if there weren’t, it looked like there were because “help me screw this rich guy” is a really common scam tactic.
Every time this wanders across the front page of HN, I wonder:

What are the chances this is more a description of the murkiness or opacity of a dark sea (compared to water near the shore) rather than the literal color of the water?
The Kate Editor – Initial Rust LSP Support Landed, Improvements Welcome
I’m genuinely curious about the answer to this question. It’s confusing me that the impression from any scientific source is that 1.5 is long gone, 2.0 is a pipe dream and any likely scenario is far higher, and that is if we start to implement drastic measures right now. Yet even the most hardcore “green” politicians talk about the issue as if we can drag our feets another decade or two with minimal impact on current generations. Why the big gulf here?
great, now you have a native client but now your customers will expect that it works offline, so now you're building a sync system for your app.

additionally, if your app has any design/layout issues, now you need to hire for people that can do visual layout using tcl/tk.

If your app consumes rich text, you're in for a real treat as you are now on the hook for figuring out how to manage that as well (in addition to serialization, you also need it to likely be emitted into some web friendly format anyway. if your app consumes some feed (say new-user facing features or whatever), you need to find some meta-format that your app can use to layout that content (or i mean, i guess you can use a webview, but then...)

if your customers are enterprise-ey, you are now dealing with some overzealous IT dept that is skeptical of your application running with user permissions.

if you're trying to push a fix/update to your users, you now need to build infra around deploying new apps as well as customer support determining if users are somehow running old versions when they report a bug.

the web is a total "mo money, mo problems" situation, but i think people dismiss how many problems the web solves for your developers on a day to day basis: easy to push updates, simple to whitelist your app's domain on some restricted network, easy add dynamic content/layout to portions of your app with stored content, (less sync resolution issues because your app probably requires network to operate) etc. Native apps have their own issues, they're great, don't get me wrong, but people demand a lot from basic apps of any stripe these days, and as those requirements increase, so does the amount of complexity that developers need to manage at all stages of the pipeline.
Tell Me What You Want Out of Your Holiday and I’ll Tell You Where to Go
I'd think that, if they stopped providing value, the movie theaters would just undercut them?

After all, you probably spend more time in the theater than interacting with the moviepass service.
movies are profitable for some of the parties in the chain, but the theaters specifically must pay so much in licensing fees that they don't make much on a given ticket.
... the research that almost certainly hasn't been reproduced even once?
It's also existed in the UK[1] (and France and other EU countries IIRC) since the 90s, which I suspect also proves the business model is viable (at least in some territories, and I don't see why in principle it couldn't transfer to the US).

[1] https://www.cineworld.co.uk/static/en/uk/unlimited (unlimited 2D movies for ~£20/month)
What tech you use is much less important than the way you use it. If you build great stuff that works well your clients will be happy, and they'll give you more work. It's not complicated.
Yeah, because the people hiring you have no clue what kind of a maintainability hellscape you're leaving for the next person...

Also I'm 97% sure I could own your site in under a day, based on how home-baked you just said it is, and I'm garbage at pen testing.

Healthcare site, you say? Jesus Christ, I hope they have data breach insurance.
It'd be like writing public articles attacking your company's accounting practices. Sometimes things are so bad it's fair to blow the whistle, but it creates nasty incentives if companies can't perform private security investigations without risking a public shaming over the results.
Alternatively: provision a Heroku dyno, add a single-line Procfile, git push heroku and you're done.
This, definitely. Many of the "X should learn to code" arguments really miss the key point that X is professional, specialized skill and clients pay for that skill.

The primary other way that "learn to code!" come up is idea/assertion that programming is like literacy. Now, I like the idea that programming is like literacy but we have to consider that programming has so far not shown itself to be like literacy at all. So far, programming has been much more like law or medicine, a specialized skill set. The amateur client who knows a little bit of law, medicine or programming, from the Internet or elsewhere, just makes things harder for the professional (whereas a literate client is better for a lawyer or any professional and literacy gives many non-professionals are skill to develop throughout their life).

Which is to say we should recognize programming as a professional activity but keep working on things that might, in the future, open the door to a programming as literacy.
This is a win for Uber and Lyft. (wasn't Uber lobbying for this in all big cities?)

Once it becomes the norm, Uber/Lyft can continue jacking up prices.
Article feels like it's focused on breaching the critical systems rather than just trying to kernel panic/overflow/etc them. My concern would be that if you could mess with the ODN such that it could crash or disrupt the data flow of either the other two systems I suppose you might brick the plane (because they refer to a "bridge")? Who know though, maybe there are redundant systems that can handle multiple critical failures, article is so light on details.
> Boeing maintains that other security barriers in the 787's network architecture would make that progression impossible.

They probably do something to that effect
I know researchers have found how the ancient Greeks used to paint their sculptures, and that they used blue, green, and red as separate colors (https://www.smithsonianmag.com/arts-culture/true-colors-1788...).

I always considered that phrase in Homer as a poetic flourish, or maybe just something that was a figure of speech in his time period.
4 out of 6 people in my cube farm own airpods. I see them everywhere. These things are incredibly popular with the under 35 demographic.
> javascript rules, and you can't build truly interactive sites without it

But does the website you're building need to be interactive? Usually not, unless it's a webapp. (Maybe for form validation but that's pretty much it.)
> The company administrators, doctors, practitioners, etc... are so happy with the new no-nonsense site that they raved to the parent company about it.

Any reason they liked it in particular? Faster? Better/cleaner UI?
Everyone (well almost) wants a server-templated site or at the very least a functioning back button. No one wants to sit and wait for 3 million lines of JavaScript to parse and run with every press of the back button (and probably not even get to the same state as before!).

Yes, I know there are some stellar SPAs that actually work. But I can't see why they're necessary 97% of the time and it really bothers me when I see a SPA where one isn't needed that breaks basic functionality like back buttons and right-click and all that other jazz.
Valve in general seems to be vague on the entire concept of multi-user. They have a family plan where you can share your library with your family, but with the limitation that only one member of the family can be playing a game at once.

Even if you are trying to play two different games Steam will try to kick one of the players off. It seems like they think a "family" is a family of computers that one single person might want to access. I get that they might be concerned that someone sets up a Steam account for their entire floor of the dormitory or something, but wouldn't a sensible limit be more like 5 instead of 1, with the additional limitation of only one copy of a particular game at once? Plus the ability to buy multiple copies of a game for a single library if you want? Netflix, Amazon Prime Video, Hulu, etc... all figured this out, why can't Valve?
Yet, weirdly enough, if a food item had all of those qualities except being calorically dense it wouldn't make people fat. Everyone one of those factors are things that lead to over eating, when paired with calorically dense you end up with the chronic over nutrition mentioned in the title.
> the only way you're going to not get fat from putting 5000 kcal a day into your pie hole is if you have significant medical issues with your digestive system.

As someone who, down a few hours of dance practice a day from my peak activity level, is running about 4,300kcal/day burn rate, I can imagine other ways to not gain weight on a 5,000kcal/day diet than “significant medical issues with your digestive system”.
It means the underlying problem is not the tooling, but the use of the tooling.

In other words, "I can choose the correct tool but still fail from poor approach of problem."
The Long-Term Effect of ABS in Passenger Cars and LTVs [pdf]
This is a great app for those without managers or girlfriends. :)

On a more serious note, I get it, but realistically how much can someone stick to it for a reasonable amount of time in order to get conclusions?
> What to Submit

> On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity. [0]

[0] https://news.ycombinator.com/newsguidelines.html
Do you think anyone goes into a project thinking: "I'm going to build some complete garbage"?

Shifting project and business requirements, scope creep, poor design choices and lack of competence all contribute to what makes bad software.