skysight-inc/HackerNews huggingface dataset:
Why you should care: it's relevant to the post-BDFL continuity plan, because 1) the stressors that pushed GvR out will also act upon the new decisionmakers, 2) those stressors can be reduced, and 3) change-of-control is innately risky and we should be extra-worried (at this moment) about existing, important stressors.
I would assume it's because not every thread may be busy at the same time - some may be waiting for I/O, or simple keep-alive threads that only need to do things once in a while.
>NeXT was laid out somewhat similarly, but with less convenient common areas.

Fascinating. I've always found Conway's Law [0] to hold up incredibly well, and there's a perfect example.

[0] https://en.wikipedia.org/wiki/Conway%27s_law
For awhile the 'e' key was only working about 90% of the time. Then it began working about 120% of the time, so I had to remap it to nothing, move the 'e' to the backslash, and plug in an external keyboard. The trackpad and all the rest of the keys were working just fine. I usually replace machines every three years or so anyway, so the key issue was just the trigger. Thank you for your advice. Do you think that might be the issue, given that the trackpad worked fine?
Yoga book isn’t Apple. People were saying the exact same thing about iPhone vs Blackberry.

If done right, it is completely possible. But the old neck beards will certainly have a conniption fit.
Read "The Lean Startup" by Eric Reis. It's entire premise is dealing with uncertainty.
I doubt he had that honor. Lot's of people call her Hitlery. This is one reason she has that title.

* https://www.youtube.com/watch?v=mlz3-OzcExI

* https://www.youtube.com/watch?v=wknw5UwClFI&bpctr=1531431778

* https://www.un.org/africarenewal/magazine/december-2017-marc...

To you, somebody calling her a name is not honorable. You don't care what she did to earn that name.
I share your sentiment. I worked for a company that leased an old Sun building - all of the engineers got a private office. Three solid walls (unfortunately exterior windows were limited) and one entire wall was glass and frosted between knee and shoulder height. The door to the office was a floor-to-ceiling sliding door on this glass wall.

The offices all had whiteboards on two walls and were large enough to comfortably fit 3-4 chairs total. This was great because it meant any useful meeting could happen in anyone's office. There were larger conference rooms on the corner of each hallway which had screens for video conferencing and larger tables to accommodate larger groups of folks.

If you needed privacy to focus, you closed your door. If you were open to watercooler-chit-chat, you left your door open. It was easy to overhear technical conversations if you wanted to, but also easy to ignore since you had 3.5 walls of noise privacy.

At the time I did not realize how good of a work environment that was. It was almost a decade ago. I still consider that my ideal work environment if I have to work in an office.
I apologize for bringing up something that is offtopic here but I am really glad to have read your comment.

Last I read in the docs, Memorystore was not accessible through the AppEngine Standard Environment, which was rather disappointing to me.

I was wondering if just providing the App Engine Standard Environment with the Redis instances address and credentials, along with a service account or IP whitelist for access, would not suffice to be usable there as well. If I'm not wrong, something similar is done in Flexible Environment according to the docs.

https://cloud.google.com/memorystore/docs/redis/connect-redi...

Thanks so much!
Just like communism, if in real life 99% of practitioners are doing it wrong, maybe we should revise the theory? Some dreams have a strong attraction, but they’re just like the mermaids of old.
Whoa, you are trying to compare WalMart to Costco. They are different companies with different concerns.

WalMart is concerned about employee happiness and satisfaction. The actions they take are not the actions that other companies take. Their employees are happy enough with the results for WalMart to be satisfied with them. That others do different things (which may or may not achieve different results) is not important to WalMart. What is important is their return on investment, they have determined that more investment wouldn't be worth it.

Of course as outsiders we can look on WalMart and make value judgements. I wouldn't want to work there. I wouldn't want to work for Costcot either. YMMV.
the only viable linux platform remaining is the one loosely organised and licensed around the world called "Android". with recent advances in ARM64 chips and extremely fast processors some OEM's are releasing desktop modes for android. Its truly the final frontier of linux, hopefully this idea can aleviate those issues you've had with linux. Applications work consistently on Android although there is still the app gap of stuff not yet ported onto google play store.
I don't see it as mystery as why it happened. Perhaps you are thinking there was some specific trigger for his stepping down. I don't think so. When the language becomes as popular as Python has, the head of the project is going to become a target for a lot of unwanted attention. The "assignment expression" PEP was a good example of that but not the sole cause.

Even if infuriating jerks are 0.1% of the population, when your language has hundreds of thousands of users, you are going to deal with a lot of jerks.
Frankly, I'm surprised he lasted as long as he did without going mad or something. I would not wish for any of my friends to be subjected to that kind of attention.

We were very lucky to have him leading the project for so long. Python will survive without a BDFL and I hope he enjoys the vacation.
running more threads than CPUs is useful whenever your workload is not 100% CPU-bound. a DB workload is likely IO-bound, so many threads will just be sittin' there waiting to be woken up a lot of the time
> the elected component of the government sector in a properly functioning democracy is far more mortal than large corporations

The elected component of any modern government oversees a vast administrative bureaucracy. This is the part people refer to when comparing "big" and "small" governments.

> the main reason for the institutional inertia is the same scale, complexity and principal/agent problems large corporations also suffer from

Federal bureaucracies only die if (a) the legislature explicitly kills it or (b) the government collapses. Large companies, on the other hand, can go bankrupt. Shareholders are motivated to be ruthlessly efficient in a way lawmakers, somewhat by design, are not.
That's actually a strong argument for requiring a 'super majority' to decide any major decision.
Do not go to law school unless it's a passion that you're willing to sacrifice financial and mental well-being for. It's only "worth it" if you're able to attend an elite (top 10) institution -- otherwise, in an industry obsessed with status and prestige, you'll end up on the wrong side of the bimodal salary curve¹ struggling to pay your six figure student debt. BigLaw, IP (patents), and tax attorneys are the only specialties that make decent money. Once laden with debt, 2000 billable hours is standard at most firms, meaning that 50+ hour weeks are the norm. Lawyers are unhappy: alcoholism² and depression³ are rampant in the profession.

Source: Lawyer that hated writing patents and went back to tech.

¹ https://www.nalp.org/salarydistrib

² 20+% of lawyers have alcohol problems: https://www.americanbar.org/publications/youraba/2016/march-...

³ 4x rate of depression and highest suicide rate among occupations: https://www.americanbar.org/publications/gp_solo/2015/march-...
I care that those concerns are being addressed. I do not care whether they're addressed in public in a way designed to mollify any particularized concerns I might have, because I am not a member of the Python core team, and they don't owe me that.
I use an ergodox with escape mapped to a very easily accessible location. On my laptop keyboard, I have caps lock mapped to escape.
It's a mostly-black screen with fairly low brightness. I'm not in the habit of sitting in a pitch-black room on my laptop, so I can't tell you how it looks there, but in my everyday use it hasn't been even the remotest problem.
I would have thought that for the time and cost of doing that, they could just ship the CD with a booklet of photographic instructions. An instruction manual SO SIMPLE that even a scientist at the South Pole could understand it. Or they could make a video chat call and it could be explained.

(I don't mean scientists are so dumb, but that they might have Antarctic Stare...)

https://en.wikipedia.org/wiki/Polar_T3_syndrome
ya its an arrow bud
What’s the long term plan here with StackDriver and OpenCensus?

Are you eventually going to support high cardinality events with the ability to aggregate and then break down (as opposed to say Prometheus which pre-aggregates, so you can’t break down to debug, and doesn’t support high cardinality).
I've worked with teams big and small, mostly as an individual contributor, and the issue with not having a good team culture is you get churn. You can't have good team culture when half of your teammates are just at home most of the time, or if you're at home and the rest of your team is in the office. People jump around companies too often because they get jaded, bored, enticed by better offers elsewhere, and without team camaraderie and connections that bind the team together personally, you're going to get a high churn rate.
Having been playing with Windows 10 recently since not using it more than an hour or two at a time since Windows 2K, it was pretty amazing how much of Windows really hadn't changed, and how much old chrome there is in there.

I'm not sure if that's more due to a "don't fix what isn't broke" attitude, that Microsoft is obsessed with features rather than fixing things, or simply the sheer size of Windows.
I’ve been using AppEngine for years and really like it. Had an interesting billing issue recently.

I enabled a task queue to run a longer running task in the background but I didn’t realize there’s a default to retry failed tasks indefinitely. This started slowly increasing my front end instance hours (and my bill). A few hundred bucks later I figured it out and specified a retry attempts limit.
in system settings under keyboard you can set it to only show the function keys and act only as a row of keys (similar to how it runs while bootcamped into windows)
If you’ve ever used a serverless framework, you’ll know this argument falls apart the second you need to run something for a long period of time, manage complex state or glue services together. There are numerous other details being glossed over.

The servless approach has its place just like everything else, it’s not a panacea though.
It simply means that your safety isn't worth trying to save a few thousand dollars of some corporation's equipment.
I think you're probably blowing it a little out of proportion. I'm sure he'll give guidance and advice to people (who ask for it). He said he would he would still be involved as a core dev after all.

That said, had he given (say) 2 years notice, I still think he should not name a successor nor make those decisions himself since the community would need to learn to govern itself anyway.

This is a sad day, but the sky certainly isn't falling.
The new Macbook keyboards have such low travel that they feel like a step in that direction. I like the laptop overall but I make a lot more typos than I did on my old one.
Always use /

Windows can, surprisingly, handle it just fine.
Yo, I'm with that company doing the AV scooters and bikes, and yes it's much easier to nav than a car, we're looking at two magnitudes easier as far as computing power. We won't do autonomous with riders on-board so we can go slow and be conservative. Sensors are more than two orders of magnitude cheaper, we can use ToF laser rangefinders that are close to mobile phone grade.
A very casual observation by me is that open office favors shallow work. Things that can get figured out quickly. Same for decisions made in large meetings. It doesn't work well for problems you have to work on for weeks and where there is not a clear path.

Just my personal observation how open office or a cube farm with loud neighbors affects me.
As a big influencer, Guido, "the creator of python", even inspired austin powers character

Guido (1995) https://gvanrossum.github.io/images/Guido@200dpi.jpg

Austin Powers (1997) https://m.media-amazon.com/images/M/MV5BYWY1ZTdlZTEtYWRjOS00...
I wish I had some good takeaways from my first and only experience as a dev lead.

The Good:

- I came in with a blank slate. They had no source control, no CI/CD, and two "database developers" using an ancient platform with only passing knowledge of any modern language - C#. I was able to implement best practices and teach them how to code in C#.

- The developers were eager to learn and were smart.

The Bad

- The company moved the entire project to AWS but to get anything provisioned I had to go through both my manager, the net ops people, a bunch of hired consultants, and an outsourced cloud management company. I never did get access to anything outside of some EC2 instances.

- None of the people involved knew anything about AWS besides how to translate an on prem network to AWS and then wondered why it costed more.

- I had a budget to hire, but only contractors. All of the best developers wanted a full time job with benefits. I never got the cream of the crop.

- When the company was acquired, they decided that they didn't "want to be a software company" and wanted to outsource everything. They did however want me to lead two more projects to completion. I stayed long enough to finish phase 1, but it wasn't the best implemented thing in the world. It was architecturally sound, but didn't leverage anything AWS provided.

- Everyone above me was jockeying for position at the newly merged company and didn't make development a priority.

My solution:

- I left for a job that pays slightly more where from day one I was given AWS admin access (yes I had the qualifications and experience). I'm now "just" a Senior Software Engineer but I am nowhere near as hamstrung when it comes to getting things done.
Does OneDrive count?
I don't know if it's just me, but if you read the forums and bug reports related to open source projects, it feels like programmers today are a really entitled lot.

The tone that people take when filing bug reports for what is basically free software is reprehensible. People are doing work for FREE to benefit you, and you take a tone with them like you are a prince and they are your royal goblet holders? Who taught these human beings their manners?

I totally understand the frustration when you write a large system in Python and then the Python committee makes a breaking change that makes your life very difficult. However, you didn't pay for Python! These sorts of changes should be expected, and if you didn't expect it, you are the fool. And in any case, you aren't paying these people a cent, so speak politely to them. You are basically a charity case from their perspective.
Facebook. It didn't do anything besides what myspace did except the "cleaner college-aged" marketing.
Would you be willing to add a contact method in your profile (twitter/email) for some offline questions?
That's what I don't understand- there is plenty of room for both, especially on the 15". Just add the Touch Bar strip above the function keys and call it a day...
> no IO is performed
Machine Zone Shuts Down Its DSP, Lays Off 125 Employees, Including Media Buyers
The Touch Bar can't be dimmed below a certain threshold (either manually or programmatically). Normally we use f.lux or Brightness Slider to dim the main display, but touch bar brightness can't be controlled. Makes it hard to work late at night without putting electrical tape over it.
Yeah, it's sad. I was hoping for a version without a touch bar too :(.

I'd also say that these new Macs are the most unpopular ones among devs. It's just that we are so used to MacOS :|
FWIW you can do C-x M-: instead of C-x ESC ESC
The author harps on "networks" too much. In general, brick and mortar retail sectors which can be done better on line have tanked. From Sears to Radio Shack to Toys-R-Us, that's happened. Malls in general are hurting badly.
Yes, and we need more hackers in bioinformatics and RSEs or Research Software Engineers.

If you are a data scientist or software engineer and are looking for a new field that really needs your help check out computational biology and/or bioinformatics.
I spent some time thinking about ways to incentivize patients to upload bills, you'd only need a very small fraction to get a representative sample of how much different services cost at different hospitals. I haven't come up with anything very motivating, except maybe the desire to expose how ridiculous some of them are.
I cut my teeth on Windows with Microsoft Visual Studio Basic in the 2000s, then Windows/Dev-Cpp because of poor MSVC++ support for some C++ features I thought I needed at the time, switched to Mac/Vim, then had a 6ish year stent with Ubuntu and Vim as an IDE. But then a botched upgrade from 14.04 LTS to 18.04 LTS lead to a few frustrating hours of my time to get X to even load. I'll never see that time again. Now I'm back on Windows, and somehow have drudged along without installing Cygwin yet, although that's coming. Developing Java has been a pleasant experience with IntelliJ IDEA. The GUI use is taking getting used too-- but configuring IDE things like language servers is mostly automagic and have very reasonable defaults. The biggest issue I've had is Windows upgrades requiring random restarts completely interrupting my workflow. But, overall, rediscovering Windows has been a pleasant experience for me too.
Most likely the change is from cgroups, and not systemd itself. This could be verified by booting with and without cgroup_disable=cpu.
C++Now 2018: Michael Caisse “Modern C++ in Embedded Systems”
We'd love to as well! Unfortunately we don't have a public timeframe we can share yet :(.
in bootcamp the touchbar continues to function independently and acts like the function row of keys
In addition to all the good advice already given: this question has (at least) three different dimensions:

- what would be best for your company?

- what would be best for your team?

- what would be best for you?

Try to come up with answers for these questions separately. In particular, find out what is important for you personally (making a career, gain trust with your team, being open and honest, etc.). Identify the communication strategy which optimizes the outcome for you, your team, and your company.
Much of that was also back before viruses and trojans were an every day occurrence, before an unpatched computer on a network wasn't going to be owned within an hour or so.

It was more fun back then, and we weren't the ones who ruined it.
That sounds like a perfect setup! Mind sharing the modification rule?
Caching effects. If you have an x-thread CPU and you split your workload into y >> x parts, it might happen that suddenly a workload fits into a faster CPU cache level (e.g. L1 instead of L2) and then you see huge speedups. I've seen things speed up manifold when I had 67 threads and added one more even though it was an 8-thread CPU. Keep that in mind when you do threading.
Imagine not being able to mute your sound in public because your finger doesn't have enough capacitance for some reason.
Exactly, our mistakes are not inherently catastrophic. Stability is actually much harder than navigating.
Notepad was probably the only remaining part of the operating system that didn't spy on it's users to send personal information back to Microsoft and it's advertisers.

I'm sure that will now change with the latest updates. I mean why shouldn't a basic text editor send user data to the internet.
JavaScript parcel tree shaking lodash (bonus rxjs)
Given it depends on the kernel version, I would imagine some kind of platform-specific tuning. Epyc is a NUMA platform, so perhaps improvements to the NUMA scheduler?

That's pure guesswork, though.
> Exactly. Docker files are worse than war files in pretty much every way.

They focus at far too low level a problem.

> The problem is that testing isn't cheap. This is where microservices and containers and the all this craziness will fall down. Now you've got dozens and dozens of applications all running with their own application servers, JDBC drivers, and their own JDK. This is a combinatoric explosion in your testing surface.

I fail to see how this more difficult from 95% of existing enterprise systems that run various JDK versions, various WebSphere versions, JDBC drivers etc.

The difference with containers is that vendoring your dependencies makes all that explicit. Whether you choose to stay on old versions is a mistake you can still make (and will make if you leave container creation and patching in the hands of dev teams).

That said, since when does any organization build horizontal testing libraries, like, "test X version of JDBC", so they can standardize on a single driver across all projects? It's never done. Projects are all over the place with their dependencies unless there is institutionalized forcing through Maven repos or what not to block the download of old/insecure versions.

There is no combinatorial problem here, each test suite needs to unit test the individual service and then test the API contract of the service. If you let your dependencies decay you're accepting major security and maintenance risk, but you were in the WAR file world too.

> The true value of the application server approach is that it forced applications to conform to a clear contract. Once your application conformed to this contract it could be thrown over the wall into a full-time ops organization that could transparently deploy, monitor and manage the app.

LOL, I really think you're exaggerating. I've worked with WebLogic, WebSphere, IIS, JBoss, Tomcat, Django, Rails, Node, you name it over the years, and while some orgs got close in the Java world, this was mostly a pipe dream that never happened in any cost effective manner as a standard practice.

> The container madness will come to an end. People will realize that giving developers the keys to the kingdom and total freedom over their application is a terrible idea. (And smart developers don't want total freedom.)

This I agree with. It's all far too low level.

This really was Docker, Inc.'s fault IMO, their marketing message was to empower developers to get ops out of the way by building these containers that would magically just be run as opaque lego blocks. That was the hype everyone on HN was drooling over in 2013. Turns out it's not quite that simple.
I've never understood why they don't license something like notepad++ for $1 a copy, or build their own internal version. The value add creating good default tools instead of paint/notepad/calc/space-cadet is pretty huge.