skysight-inc/HackerNews huggingface dataset:
Yes, the large gap down is a given, since 7.5% was already in after-hours. I guess I was thinking more long-term overall dive than daily. The markets have been pretty volatile for the past month or so. It's odd but a one day 500+ Dow drop isn't really unusual at this point.
Lenovo offers a next business day on-site replacement warranty that covers accidental damage. It doesn’t get much better than that. I’ve used the service a few times over the past five or so years and it’s been excellent.

It really wasn’t that much extra, and it’s a no-brainer when you consider how valuable all the lost time from a multi-week replacement.
Model 3 delivery is 100% North American though
I prefer that you stay behind me until it's safe to pass (that is, you can change lanes to pass) and I won't see you again thirty seconds later at the red light.
This is not what democracy looks like in Eastern Europe. Instead, this is how democracy goes off the rails and is replaced by something else.

I agree with Fidesz's anti immigration stance, but I what I don't agree with is eroding democracy.

Romania is practically led by crooks who also got elected democratically. Now they're eroding democracy and the judicial and giving themselves a get out of jail free ticket.
I wish it was that simple. First there is battery life and surprisingly some foreign carriers block tethering features like Personal Hotspot. As an example a SIM card I've got from Softbank in Japan in 2014 only allowed me to connect to their network after I've installed a profile that disabled tethering.
Yes, I do realize that we use our phones much more than laptops. But again, everything that the iPhone does a cheaper phone does too, may be crappily, but that's all they can afford and it works for their needs. You can't solve every problem with financing because eventually you have to pay that.
oops, no wonder I failed in math test at college .
Just a theory but I’d bet, for companies like Google and Facebook, grinding leetcode would be less work and more efficient if your only end goal is to work there.
You can just type "current temperature" in google and it'll give you the weather forecast for the week. At least with google, they already have all your data.
OR JustPack?

I remember one of the main Goal of WebPack 5 was sane defaults. ( I cant find the post anymore ) So hopefully the WebPack team can learn a lot from JetPack.
It's mathematically different from Monero, and is thought to be significantly more secure. It also has some very interesting properties like allowing the blockchain to be represented in a totally different way, using only a tiny amount of data.
Or you are driving with perfectly normal situational awareness, multiplied by enough hours, and sometimes you hit the low end of the bell curve.

Checking is far more reliable.
I drive cars that get a bad rep for visibility. This is the advice on mirror adjustment I swear by: https://www.caranddriver.com/features/a15131074/how-to-adjus...
There are examples of this. Lerna revokes licence to companies working with ICE[0].

RedisLabs moves to Apache 2.0 modified with Commons Clause for their modules[1] to exclude cloud vendors who don't contribute back to open source. Note Redis itself is still BSD licensed.

[0] https://motherboard.vice.com/en_us/article/8xbynx/major-open...

[1]https://news.ycombinator.com/item?id=17814386
Bicycles don't ride on sidewalks because you want to maximize their visibility. Most deadly accidents between bikes and cars happen at intersections where bikes are getting right-hooked by drivers who forget to check their blind spot. Drivers don't expect objects traveling at 30km/h on the sidewalk, so they're even less likely to look. Sharing the road between bikes and cars is much safer. There would be almost no problem if cars respected safe overtaking distances and switched lanes to overtake bikes.
Most frequently, I see teams B, C, and D in a polyrepo world do the worst of all worlds: take dependencies liberally, pin them in place, and try to forget about them.

This has been my observation as well, minus the value judgment. Why is pinning dependencies and moving on with life the worst thing in the world? As you point out in your article, a security fix in A does suddenly force B, C, and D’s hand. Another scenario I’ll add to that: if A provides communication between B, C and D, a synchronized update to all dependents might be required.

Thing is, I’d argue these scenarios are the exception to the rule. If you’re drawing boundaries in the right places (again this may come back to contract design) you’re largely free to change implementation details when you need to, on your own terms, and not because some distant transitive dependency has decided it’s time for your build to break.

With monorepos I see lots of the latter. Lots of breakage for no other reason than “everyone needs to be on the same page.” Lots of conversations — O(N^2) conversations, times some constant factor — that might not need to take place, ever, but it’s critical the entire company have them right now because the global build is broken.

Here’s another way of looking at it. Until a few years ago, it was standard practice to frequently update npm dependencies against fuzzy semvers. Now most people pin their dependencies, and their dependencies’ dependencies, with a lockfile. And in other ecosystems like go’s you also have tooling to support much more controlled, infrequent and minimal dependency upgrades (see MVS).

Why the change? Because people got tired of things breaking all the time. They wanted off the treadmill so they could Get Things Done again. I don’t see how monorepos provide this stability, and frankly it seems like the monorepo idea is where npm was about 5 years ago. Perhaps even farther behind than that, since C, C++ and others haven’t even evolved viable language package managers yet.

You’re a rust fan, so maybe cargo + a monorepo is a sweet spot I haven’t encountered yet? Anyway, I do really appreciate you taking the time to share your perspective on these things. It’s been great having a reasonable discussion about them.
TED talks are infotainment. Pornography for people whose vice is feeling like they've been inspired and gotten smarter. In short, they ring false.

It feels like you're learning something, but the lesson plan was devised by a marketing department for the idea. It feels like the primary motivation is how good of a story can be told, and not the actual truth.

"Popular science" in all its forms – sucks. Leading people to believe things because they're told in a certain way that makes them feel good. The problem is you don't get to truth because the explanation is easy to understand and intuitive. Lies are easy when that kind of explanation is common.

When you're actually learning things, you need to be able to substantiate the facts, not just have statistics and study results thrown at you by an engaging speaker. In real science classes they make you drop balls and measure currents and synthesize chemicals and do calculations.

I also loved TED talks when I was younger.
Hey Max! Remember drinking beer on Caltrain?

Awesome to see your post on HN! Hope all is well :)
Yes, nuclear would eventually have been pushed out of Germany's generating mix as higher renewable penetration demanded more flexible complementary generation. But it wasn't going to happen this soon. In 2010 the German government agreed to extend nuclear plant lifetimes by an average of 12 years, into the 2030s:

https://www.bbc.com/news/world-europe-11194117

The German government reversed course less than a year later following the Fukushima accidents. 8 German reactors were shut down swiftly and the 9 others are scheduled to shut down by 2022. German coal consumption and emissions rose above the 2010 level for multiple years after the 8 reactors stopped, and I expect a similar effect after 2022. I understand that the voters wouldn't stand for reactor life extensions after Fukushima, but this reversal definitely made decarbonization slower and more expensive.

The other thing that seems to be impairing German decarbonization efforts more recently is that they're not shutting coal plants as fast as economically feasible. The plants provide too many jobs. Germany has efficient, new, idle combined cycle gas turbine plants like Irsching Power Station:

https://uk.reuters.com/article/uk-uniper-irsching-notificati...

Given the downward trend of European gas prices it seems like shutting down some old coal plants and buying fuel for these modern gas plants would be a pretty affordable way to reduce emissions at the margin. The gas plants are also more flexible than coal. But gas plants need only 20 or 30 people to operate where coal plants of equivalent output need hundreds. So Germany delays the retirement of dirty, inefficient coal plants as a sop to the economically depressed regions where they are concentrated.

https://www.nytimes.com/2018/10/10/world/europe/germany-coal...
What is the obvious way to write a string constant which does not contain a newline, single quote, or double quote? Should I write it: "this way" or 'this way'? PEP 8 explicitly says there is no preference.

Sure, they have different semantics. But the Zen of Python suggestion isn't usually interpreted to accept, say, a 99% overlap in functionality.
Wow, that project is amazing. The site design is confusing though ;) A more linear design like Wikipedia is good for parents, who are usually the ones reading things like this! ;)
Refcounting comes with its own in-thread gc pauses whenever you exit a block or context and the local variables are collected.
If you ever get a third party penetration test, this is like, the first thing they find. To say "no one but attackers cares about," is pretty nonchalant – we immediately patched up this clearly bad attack vector, despite it not being extremely likely to manifest as a serious problem to us, because, like, you should just do that.
> Bytecode interpreters don’t work on the AST directly. They work on preprocessed ASTs. This simplifies the execution model and can produce impressive speed wins.

In comparing a bytecode interpreter with an AST treewalker, and assuming parsing is not counted (i.e. we already have the AST), what makes bytecode interpreter faster?

Walking a tree doesn't seem like that much of a performance penality... perhaps the "execution model" includes something else?
10,000 hours checks out. At 8 hours a day, 5 days a week, that's 4.8 years to master say a technology, language, or software stack.
I find this MDN JS guide very helpful. Quickly scan the chapters/sections and pick ones you are not familiar with.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guid...
Suppose to be once per request and short-lived. But that's not specified in the thread above.

Previous person mentioned logout, so I assumed we were talking about session tokens--which I understand its a misuse of JWTs--and is why he/she's mentioning it.

But if we're talking about just one time auth tokens, then yeah, you don't need expiry ahead of the expiry time, and it's plain it's a non-issue.
Battery life was an important consideration. The trip from Ulan-Ude to Khabarovsk takes 3 days on a train that might have or not power outlets on the coupe cabins depending on your luck. The power supplied from these plugs seems to take ages to charge the the iPad. I also had 2 Asus 10050 mAh battery banks with me that can charge the iPad from 0 to 70%.
Redditor finds plea for help from a Chinese prisoner in clothing from Target
At the times that an automatic most easily lets your attention wander, driving at a consistent speed, a manual does no more to keep you engaged.

It keeps you more focused on the car at lights and turns, but that might be a bad thing. I want to be focused on the cross traffic, not my engine.
I have plenty of apps running on my non-ARM Android devices.

As for Hyrum's Law, since Android 7, any misbehaved app that tries to use non-sanctioned NDK APIs gets killed by the OS.
>This is clearly an exaggeration.

I would argued it is not. Many had tried to make "Smartphones" for years before Apple. None of them succeeded. And Android prototype were like blackberry before the iPhone announcement. People often look back and think what we have today was so simple and inevitable, but when it actually first happen it was pure genius.
I am not sure which part of the statement you highlighted you asserted is wrong? That:

a) Growth doesn't require work?

b) Work doesn't require energy?

From what you included, since 1980 to 2016, energy usage has doubled, from 281btu to 572btu [1].

Yes, we can become more efficient with the energy we use, but we still use energy, and we still use more of it. If we can use energy without generating heat, then we are good.

Additionally, dangerous part is that, as we are more efficient, we find new use of resource that gobbles up the efficiency gains. [2]

[1] https://www.eia.gov/beta/international/data/browser/#/?c=410... (scroll down to chart to see world consumption)

[2] https://en.wikipedia.org/wiki/Jevons_paradox
For cellular on laptops and tablets to become standard, the networks should stop charging us extra for another device. I wish I could just be charged for each gigabyte of data without regard to which device is using it, just like Google Drive storage is available to all your devices without a per-device fee. As long as there's a separate fee, most people wouldn't want it.
Every app is supposed to paint itself on any UI toolkit.
If I was in a hurry I’d buy a replacement device, restore from iCloud, and then return it in a week when my original device is back from warranty.
Which specific "best practices" are you referring to?

Ignore the CSS-related discussions for now. React itself doesn't care how you handle the CSS in your app. You can write standalone stylesheets and match the classnames in your HTML output, same as you always have, write inline styles, or use one of the fancy new "CSS-in-JS" libs that have popped up.

Other than that, the aspects of "reusability" and "easier to work with than hand-written DOM manipulation" are certainly true. "Easy to learn" is just an observation, not a reason to use it.

In general, React is beneficial if you're doing any kind of interactive client-side application, regardless of how big your company is. It provides a consistent mental model for how your app is constructed and updated: given some set of state values, the resulting UI output will be X, and the data and updates flow top-down in the tree. This becomes more valuable as the size of the client-side logic and UI grows.

I'd suggest taking some time to actually try out React and get a feel for how it works in practice. The easiest way to do it is to open up https://codesandbox.io and start a new React project.

Here's a couple meta-links that may be helpful for learning more.

My suggested list of resources for getting started with React:

http://blog.isquaredsoftware.com/2017/12/blogged-answers-lea...

My React/Redux links list:

https://github.com/markerikson/react-redux-links

If you've got any further questions I can help with, ping me @acemarke on Twitter. Also, come by the Reactiflux chat channels on Discord. The invite link is at https://www.reactiflux.com .
I think you are conflating Guido's attitude to FP with Python too much here. All the FP primitives in Python were championed by other people. In your linked blog post, Guido is talking about purely functional languages and how Python, like Lisp, is not like that. Which is true but doesn't make Python bad for (or "hostile" to) writing functional code.

In fact Python taught a generation of programmers to love functional code, because of the big speedup available from stringing together C-native builtins with higher order functions.
Geography fail. Kinmen is not in Taiwan.
I suspect Apple is working through a long-term secret plan to phase out all MacOS products and replace them with upgraded iPad Pro devices instead. With some increased hardware resources and iOS enhancements, iPads could eventually meet the needs of most knowledge workers and content creators. Until that plan comes to fruition I suspect Apple will put minimal effort into their existing line of laptops and desktops.

A vocal minority of power users and developers will hate being forced onto iOS, but most customers will be satisfied. And Apple will be able to consolidate their engineering work behind a single platform.
The subway is governed by brinksmanship, and is set up so that the governor can have as little or as much perceived influence over the subway as is convenient.

The governor pushing the MTA to complete the Second Avenue Subway on time: https://www.nytimes.com/2016/12/13/nyregion/second-ave-subwa...

The subway was then found not to have completed safety testing in the sake of opening "on time": https://www.nytimes.com/2017/09/20/nyregion/second-avenue-su...

The governor lambasting fare hikes that are largely the result of his administration underfunding the agency, and blaming it on "waste" by his own administrators: https://www.nydailynews.com/news/politics/ny-pol-cuomo-mta-f...

In fact, this most recent thing happened after he decided to interrupt subway service in this tunnel for a photo op two weeks ago, despite the fact that his agency has known about it for almost three years now. http://bedfordandbowery.com/2018/12/watch-gov-cuomo-sample-t...
Grin uses homomorphic cryptography and non-cooperative coinjoin giving it great privacy. The amounts are not public and look only like random 256bits to someone that does not have the private key.
I would probably object to Bitcoin counting.

Its original notion was "peer-to-peer electronic cash". As best I can tell, there's almost no significant legal use beyond speculation. [1] Even prominent Bitcoin advocates have admitted it isn't a good currency. [2] Illegal use is self-limiting; if Bitcoin becomes mainly known as the crime currency, it'll be truly screwed, as governments everywhere will further crack down on conversion and use, driving off investors, developers, business partners, etc.

I think it's especially obvious how much it's failed as e-cash when you compare it with M-Pesa, an African e-money system. [3] It started just a year before Bitcoin, but does something like 100x the transaction volume and is wildly popular in a number of countries.

[1] E.g., https://www.nytimes.com/2018/04/16/nyregion/new-york-today-l...

[2] E.g., https://avc.com/2017/08/store-of-value-vs-payment-system/

[3] https://en.wikipedia.org/wiki/M-Pesa
I feel like this is the key comment. The other 3 replies to this (Spooky23, CodeWriter23, em-bee) all made good points.

TBH, it seems like you actually have a lot of opportunity for together-time during weekdays. It looks like everything from dinner, work out, chores, until sleep time are all together-time. Make dinner, have dinner together; don't do it alone. Work out together (if possible; unless you're each interested in drastically different kinds of exercises). A lot of chores can be done together. I fold laundry with my wife together all the time. Spooky23 said when you have kids, every minute counts -- in the sense that you want to spend time with them -- but I say, also in the sense that every minute of your time counts because there's just so much to do when you have to take care of a baby. Sometimes folding laundry together is the only time of the day when we can have some real conversations.

For weekends since she has night shifts, you will just have to accept that most weekends aren't going to be a lot of free time together -- but like others said, make her breakfast for her 2pm wake time, take her to work at 7pm, pick her up from work at 7am, etc. It's all opportunities for conversations. It doesn't always have to be dinner dates and movies.

It sounds like you work in a tech startup. Is that your own company? Are you an employee? I know quitting isn't a solution, how about switching jobs (to a remote job)? How about reducing hours? How about reducing commute at the current job (work from home more days a week)?

Unless you're a founder of your company, switching jobs is more viable than you think. A lot of times it seems like you're really invested into your job (whether emotionally or financially in the form of stocks), but a lot of times you don't even realize how much nicer things could be until you made a jump. I moved from a job where I worked with a lot of friends and have a lot of good times together but a hellish bay area commute (~3 hours a day minimum) to a remote job and life couldn't be better. I don't just get back 3 hours a day, I get back my sanity in the form of pretty much eliminating stresses (which mostly come from nightmare commutes) and energy to spend with wife and baby.
I love Blink, it’s perfect for a remote emacs session. I use esc for alt, capture CTRL-space. You may have to rebind some control sequences, I don’t have that handy, but almost everything gets passed through. Only thing I can think of that doesn’t is F key sequences, and that’s probably for lack of trying.

Edit: this is with an external keyboard. YMMV with the on screen keyboard, but I haven’t noticed any issues the few times I’ve done quick edits with it.
I think the viewpoint is not "do you really think they're going to skip using it" but rather a desire to not implicitly condone its use for evil.

Back to the topic, the graph isomorphism program "nauty" had such a license. http://users.cecs.anu.edu.au/~bdm/nauty/COPYRIGHT.txt says:

> Earlier (pre-2.6) versions of this package carried a different
notice: "Permission is hereby given for use and/or distribution
with the exception of sale for profit or application with nontrivial
military significance." These days most people use nauty via a
larger package such as Magma, Sage, or GAP, and often they don't
even know they are using nauty. Due to the legal nonsense that
large package distributors need to worry about, it has proved too
much trouble to maintain an idiosyncratic licence. I didn't change
my opinion about military use, but it is no longer part of the
formal notice. Brendan McKay (Jan 20, 2016)
"If it were the case that demand exceeds the supply for unwanted dogs"

It ain't just about demand; it's about demand among those with reasonably-provable ability to actually care for a dog.

"Kenneling a dog is much more stressful than moving a dog to a new home."

That's not guaranteed, or even statistically likely. If that were as true as you seem to believe, then these animals wouldn't have ended up in a shelter at all; they would continue to exist in abusive/neglectful homes, because obviously that's better than being in a kennel, right?

The interview process is meant to ensure (with a reasonable amount of certainty) that the dog's not going to end up right back in the shelter (or - worse - not end up in the shelter due to a false sense of trust in an abusive or neglectful new owner). Making that "easier" for the applicant increases that risk.

Even with that risk aside, the dog's going from being in a kennel situation (with a lot of other dogs and different people present) to being comparatively alone. That's a pretty sudden and potentially-hard adjustment. Sure, some dogs are able to adjust in a weekend (with or without other dogs as companions); for most, that's probably cutting things pretty short.

"It's a dog not a baby."

It's a reasonably-intelligent animal that's prone to experience PTSD from neglect/abuse. Its well-being is more complex than just ticking off boxes, even for a dog that seems well-adjusted at first glance.

I think right now you're operating on the assumption of a best-case (or at least better-than-average-case) scenario. The people who evaluate adopters of pets have to also consider worst-case, since that's, you know, their job. Sometimes they can be a bit overzealous, yes, but it's not like they'll permanently bar you from ever adopting if there are fixable issues with you adopting an animal at that particular moment in time.