skysight-inc/HackerNews huggingface dataset:
"I don't think they realised that they were talking to just one guy in a basement, so when the person asked to speak to someone in sales I came back on the phone with a slightly different tone."

This takes the "Fake it till you make it" mantra perfectly!
distcc: https://en.wikipedia.org/wiki/Distcc
Grammar pedants are the worst. It generally isn't very important if people understand what is being said. There are a few edge cases, but in general its pretty obvious.
"somewhat" a game of chance? For each garage millionaire there's ten million penniless garage tinkerers. It's a lottery.
I don't even think you need "the best fakes" these days - just have your press secretary flat out deny that something happened. If any reporters push back, stop asking them questions and/or block them from your briefings.

Works for a fair few countries.
Apparently, this has been going on for a while. It's a shame some of the people associated with Ushahidi are at the forefront of waxing "women empowerment" on social media..and fighting manels, promoting feminism.. This must be dealt with..shame on you!
I JFDI with VR. Had a stroke, got separated, sold the house in the posh neighbourhood. Now I live with my kids (part-time) in a 1 bedroom apartment ... moving to a 2 BR.

The same impulsivity that made me JFDI also made me terrible at focus and operations.

Now I make apps that make toddlers giggle, work in an almost no-stress environment where people really do leave at 5pm, and get paid twice a month.

Of course, I still have ideas and side projects...
Absolutely. I cannot fathom why they thought that SIGKILL was appropriate instead of SIGHUP, even if they made the misused choice of considering it their responsibility at all.
I remember every other book on Windows programming saying "Process creation/destruction is expensive, use thread pools (or at least process pools) instead, that's the way to go on Windows". Perhaps this mindset is ingrained for Windows QA team too - they don't have [enough] test cases for such scenarios.
You're right, I hadn't considered that. This thread makes me curious how hard replacing and modernizing the cooling system of an older fridge would be.
> Do you happen to know anything about it? I'm scratching my head how it's possible that process termination serializes with GUI…

Not anything more than what's in the essay. But possibly some (pair of) utility function calls were added for e.g. a cleanup or notification to the OS between W7 and W10 which was not noticed at the time.

> I hope you didn't mean to say that every SendMessage call is completely serialized with each other.

It's my understanding that at least a subset of SendMessage is serialised in the kernel yes, and from the essay:

> functions like SendMessageW, apparently waiting on a kernel critical region[…], deep in the call stack in win32kbase.sys!EnterCrit (not shown)

[0] https://msdn.microsoft.com/en-us/library/windows/desktop/dd7...
> I imagine that most fridges that stop working do so because of the cooling system

What else is there in a fridge that could stop working except for the cooling system?
Competition for declarative and parallel init systems would be good, but I slightly doubt that it will stay that way. The whole conflict feels very similar to the idea of declarative and dependency based initramfs, where for a long time there was basically only initramfs-tools in debian that had it, with everyone else just using a hard coded and very long shell script. If we like to talk about init shell scripts as something people avoid to touch, its nothing compared to the dark magic and undocumented mess that went on in the initramfs shell script.

Several years ago Red Hat decided they also wanted something like initramfs-tools but which themselves had developed (a remark I recall that the developers made on the mailing list), so they built a new system called dracut that models very close to initramfs-tools, in which Debian's response seems to be: "Great, someone else want to support that complex tangle of dark magic, let's use theirs!", so instead of competition I suspect things will return to a monoculture again. A good thing is that during all this, distributions like openSUSE has also switched over to dracut which hopefully shows a trend that the age of large shell scripts in the boot process seems to be over.
Ths is good, but let's see how it clashes with copyright laws since "repairing" an obsolete electronic appliance might involve its reverse engineering and at least distributing information on how to do so if not complete binaries containing parts of the original firmware along with other parts which were hacked or developed from scratch. I expect some opposition by the usual suspects lobbied by the industry.
Improving perf in VS is hard without massive rewrites. The fundamental problem is that this is originally a COM app (as in, heavily using COM to componentize itself) designed back in mid-90s. Consequently, you get all the wonders of things such as STA apartments, and code that insists running thereon.

As it gets rewritten, new managed bits don't care about all that stuff. But so long as there's one bit of legacy code anywhere in the particular flow that needs to run on STA (usually it's UI thread), you get this whole "you have 20 cores and 60 logical threads, but all those threads need to sync on STA, so everything is serialized and slow" thing.

Even for the new code, the problem is that all those old COM APIs that it needs to interact with (not just for VS itself, but also for the sake of backwards compatibility with third party extensions) are usually synchronous. So if you want background processing, you need to spawn a thread - but, of course, threads aren't free, either.
Agreed, abstraction seem to be exploding these days and I’m not even sure we are at the end of the road yet! Linux or Windows never had any trouble with essentially realtime keyboard feedback in their Terminal windows. It’s not the OS.
Ikea, at least at the time, had very affordable fridges with A++ and A+++ energy certification. I trusted the energy certification, and assumed name-brands had no significant advantage over white-labeled (since it's all Chinese import anyway). It lasted a at least decade till I sold it to the next tenant (at a profit ;)).
Why Are Micro-Influencers Powerful Resources to Boost Your Brand
I think it can be done in a way that is quite less "stop and go". When you want to reassign a chunk, mark it as such and interrupt the core currently owning that chunk so it can do what it needs to do. Once it signal that it no longer have any data in that chuck, you simply reassign it and the new owner can start using it.
Is there any project that compiles significantly faster than Chrome while being in the same league in terms of LOC? I'd like to know if you have seen such an accomplishment even if its source is closed.
No, it's not.

Humans seem to solve problems with a combination of learned stock knowledge, induction, and constrained improvisation.

Constrained improvisation is the most interesting part of that process, and the one we know least about.

It's one thing building a system that asymptotically improves over millions of trials, and then sending out a press release claiming your system is as smart as a human.

It's another building a system that learns a domain as efficiently as a human.

Compare the relatively small number of games played/analysed by a Go master on their way to master status, compared with the number of simulated games played/analysed by AlphaGo.

ML is still a rather naive form of constrained brute forcing. It's a long way short of efficient learning.
I use tmux and emacs --daemon constantly. My experience with systemd is that I need to check whether KillUserProcesses is enabled, or else systemd will kill my processes. My experience with init was nonexistent, because it never came up as an issue.
How much time do you think a member of the latter group spend on init scripts?

When I did that job, I would estimate maybe one day a year at most. But core functions just stopping working and no one knows why would have been a very big deal
I maintain a list of engineering management resources here: https://github.com/charlax/engineering-management

I think it provides a pretty comprehensive list of topics that you could chat about during your interviews. Rather than making a good impression, you should talk truthfully about those topics. Worst case you'll learn something about them. Management is a great role that requires constant learning.

Good luck for the interviews!
AddToAny
We still have a 1995 fridge that runs continuously and never had a single problem with it. I suspect even the bulbs are still original. And no, it wasn't an expensive fancy model - just a cheap Electrolux larder fridge.

So...22 years and counting? What I mean is that it doesn't prove absolutely anything. Our electrolux fridge might survive another 40 years. Or it might break tomorrow.

I would lean on the side of that 60-year old fridge being an extremely weird exception, rather than a rule or proof of longevity of old stuff.
Also; Take what is flexible and make it fixed.
If the total cost of energy exceeds the purchase cost, yes. A rough indication of the annual running cost of a refrigerator with freezer for a new model from that year¹:

1990 €110 (500kWh)
2000 €77 (350kWh)
2010 €46 (210kWh)
2015 €32 (145kWh)

Replacing a fridge from the nineties is cost-neutral after three to ten years, depending on the model chosen.

1 (Dutch): http://www.greenem.nl/wat-kost-een-koel-vriescombinatie-per-...
Indian IT, “You're Fired”
>>the target market is people who are restoring mid century homes in Socal and want a period correct kitchen

Apart from the looks, why the hell would you want 60s kitchen appliances? Clunky, loud as hell, inefficient washing machines and dishwashers are something that people not only actively search for, but are willing to pay premium for?
Twitter feeds with replies now require login
Free website builder and domain with cheap hosting plan
I was just thinking that, my A1200 never skipped a beat.
Here's the source: https://www.musicbusinessworldwide.com/spotify-is-creating-i...
You're wrong. It gets a ton of focus. Here's the largest update in years (from 10 months ago): https://research.googleblog.com/2016/09/a-neural-network-for...

It's a very hard problem. There are a ton of people at Google, baidu, and elsewhere working on it. (Source: I'm a part timer on Google Brain)
Eh, you can change the cpu buffer a bit. That's about it. PA is still a wrapper.
> But if you honestly think that all will be solved by having technical people in most positions

That's not what I said, though. I said that, if your job is to know things about the product, it helps if you are somewhat technical.
Five-Step Mandelbulb Fractal Tutorial
"We've come to the point where building the browser from scratch takes more than building the OS itself."

It doesn't. It took ~5h to build a tiny (~150 MB) complete system (Linux kernel + Yocto based "OS") from sources on 4 core PC few years ago. With modern CPU, I guess, it might be 3h or so. On the side note, the build process generated >50GB of files.
Maybe it is just me, but I don't really look for the init script to provide me a status on whatever it is that it inited. "OK" or "FAIL" is good enough in that specific context. It is the services' job to provide me with information on how it failed (or succeeded, or partially failed) through an easily and always accessible logging mechanism.

Different services have different failure modes with nuances that can never be generically captured by whatever means you chose to launch the service, in any kind of meaningful way. When a Database service stops serving data, my first though isn't "Lets see what the init system thinks", my first thought is "Lets see what I can find in various Database service logfiles" which will, 99.9% of the time, be something specific to the database service.

Inits' job in my view is "start this, and get out of the way". "Start this", and do logging, and do DNS/DHCP/manage-daemons/manage-restarts-on-fail/manage-the-fs/here-is-a-kitchen-sink/do-you-want-fries-with-that/oh-yes-and-here-is-NTP isn't what I am personally looking for in an init system, and - frankly - is a ridiculously stupid and idiotic approach from a server architecture perspective.

This isn't about the merits or lack thereof of binary logging, or the merits of whatever else systemd brought to the party. This is about needing tweezers, and being given a 500 function swiss army knife, where the other 499 functions get in the way of it being used as a very good tweezer.

Systemd is trying to be my default OS via the init system backdoor. I'll choose my own OS, thanks.
Yep, exactly, thanks. Mainly my point was "it makes sense if you consdier that the syllable break is after Glouce rather than after Glou".
Seq is odd, to me Seq('a', 'm') says it matches 'am'. Why not overload X to support filtered forms instead? E.g X() is ".", X(from_, to_) is $from-$to, X(items) is [$items] and X(exclude) is [^$items]?
Well, that was kind of my point. I doubt many fridges break because the metal corrodes or the doors fall off. A fridge is made of quite a bit of material that isn't comprised of the cooling system, and it seems like a shame to throw it all out when the cooling system could be replaced.
It must be nice to feel at home.

There is still the cheaper alternative to pack light and move often, although it also requires exercising some level of good practices, everyone feels a bit better using a freshly installed OS.

Build your own live-CD distro, use file-system snapshots, segregate data susceptible of containing malware, or buy new stuff in random shops you deem trustworthy, use it and throw it away.

On a side note, as we've seen recently, using untrustworthy sources of software like npm will without a doubt affect your level of security.

There is no complete and simple solution, AFAIK.
> moving the Win32k stuff back to CSRSS

Out of curiosity, was there some big move of functionality from CSRSS into Win32k earlier? When and what?
The little light that helps you decide what delicious snacks you can munch on at midnight. :)

And on a less frivolous note: the rubber around the doors can perish/tear.
I think the best summary of how to do this is to take a look at Herb Sutter's three article set on "Minimizing Compile-Time Dependencies". https://herbsutter.com/gotw/

"The Compilation Firewall", or pimpl idiom, is a clever mechanism for getting code out of the header: https://herbsutter.com/gotw/_100/
> This guarantee also has nothing to do with the producer, the seller has to provide this guarantee, which can be a hassle if the seller is not easily accessible.

I can imagine cases where this works against the consumer, but in most cases where I buy things, the seller is far more accessible, and perhaps more importantly, also far more exposed to EU jurisdiction such that they bother to actually comply with these kinds of EU regulations. For example, if I buy a microwave at Wilko, it works to my advantage that Wilko, not whatever company in China manufactured it, is the responsible party.
It's a lottery.

I don't think that's a reasonable interpretation of what makes someone succeed where others fail. There is an element of luck involved, but you can greatly improve your chances by doing things like working hard, understanding the problem you're solving, really talking to your customers, getting a mentor, saying no to distractions, etc. Those things wouldn't have any impact if it really was a lottery.
Running Multics under the DPS8M emulator
Most large appliances in Europe, even the cheap ones, will have some claim on the packaging like 5-15 year guarantee. However for the cheaper ones, once you try to actually use them beyond the EU 2 year minimum[1], you'll find there's all kinds of hidden terms and fees. 50$ callout, doesn't include labour, etc.

So in practice, consumers have been conditioned to just assume that nothing is really guaranteed to last, therefore just buy the cheapest one. With the exception of certain brands such as Miele who are very popular among people with enough money to drop on the high up front price.

You're right in that this could potentially be addressed other ways, for example with packaging regulations. If it says "15 year warranty", then it shouldn't have any hidden terms or charges.

[1] Although with the EU guarantee after 6 months it's technically your responsibility to show fault, with large non-moving appliances the usual assumption is it's probably the device's fault.
CSS Custom Properties are supported in React since version 15.6.0
Latest Facebook Metrics Release: New Ways to Better Understand Interactions
Don't forget Tanegashima, which prides itself on being the most beautiful space launch site.
Partech Ventures raises $450M fund
How to Stitch Samsung Gear 360 Videos into a Real VR Video?
I used grsec for a decade, both professionally and privately.

It prevented every single kernel exploit that came out during that time.
Snake oil? I ran grsec for a decade and it prevented every single kernel exploit that came out during that time. All of them.
Why I'm Not Against Extinction
Android isn't locked down. But it also isn't exactly smooth. my Android device frequently shows me white screens or startup splashes when doing something as simple as switching tasks. It clearly can't keep multiple apps in memory at once. Somehow iOS manages to produce a much smoother experience. I don't think it's a fundamental issue though. Just a matter of priorities.
Sending json over http made easy – diver.js
It's more economical to recycle the metal parts and built new appliances than to reuse existing bodies. There is no technical uniformity in refrigerator designs, so retrofitting each one becomes bespoke engineering rather than simple assembly. Costs would skyrocket.

It would probably be more efficient (from an economic as well as an environmental standpoint) to force manufacturers to design appliances that can be fully disassembled and recycled with a minimum of effort (in terms of labour and energy). That way the raw materials used stay in use with minimal loss, and buying a new one won't be a waste at all.
Would this also apply to software products?
Unlikely, for the same reason that he didn't tackle application packaging[0]: because writing a successful init system would necessitate either perfect backwards compatibility with shell scripts (next to impossible unless you're basically just copy-pasting sysvinit) or a massive coordination problem of rewriting the long tail of all the crazy different daemons people run to be compatible with the new system.

Git didn't have this problem because:

0. Version control systems don't have to interact with as many other software packages anyway (editor/shell integration is nice, but you can live without them and just run git directly from the command line);

1. There were compatibility layers that let Git talk to popular VCSes;

2. The fact that you use Git personally does not affect anyone else, obviating the bulk of the need for coordinated upgrades (there were stories, from before GitHub was a thing, of 'guerrilla Git users' in companies that officially used CVS).

These three things ensured that a relatively painless incremental upgrade path existed; in the case of init systems, it will be much harder to establish.

[0] He talks about it in https://www.youtube.com/watch?v=1Mg5_gxNXTo ; can't find the timestamp right now, but it's in the latter half of the video IIRC.
I migrated to The Old Reader (https://theoldreader.com). I even tried to wirte the emacs mode for it (just for education), but didn't manage to finish it yet (https://github.com/jerry40/the-old-mode).
i used to have the same problem, but i found after a week of using only the mac I got used to it :)
Don’t just talk to your users, befriend them
>Apart from the looks

I'm pretty sure the main reason is aesthetics. And to be clear, I only saw fridges and stoves/ranges, no washing machines or dishwashers.

There are actually quite a lot of very nice smaller MCM homes in the area, Long Beach specifically has some great ones, and they are becoming fairly popular to renovate while keeping the original design. Some are quite small, by modern standards, and I think maybe the smaller size of the appliances are also attractive, but I haven't been appliance shopping much and I've never done a kitchen renovation so don't take this as gospel.

Edit: messed up formatting
Jared does the same in the fourth season of Silicon Valley :O
Yeah Boi Is the Future of Casual Mobile Gaming
FTA and in addition to venning's comment: "In November I began traveling extensively in support of Tech Solidarity, an attempt to mobilize tech workers after the US election. All the travel meant I sometimes ignored support emails for weeks at a time."
My favourite is a small town called Towcester - pronounced like "toaster".
I'd say that's the reason it's a job at all, at any but the largest companies. 90% of a DBA's time is spent preventing or solving problems that wouldn't be there if every developer had a level of basic competence with their DB.
As far as the cyber I agree. We came in with the Internet. We came up with the Internet.
Ok, I know this doesn't help the conversation, but I kept reading "Dickhash - Dick-based, persisted hash tables".

I was so confused.
Oh, thank you. I feel a bit stupid for not just trying that URL, but I couldn't (can't) find a way to navigate there from the home page...
I was somewhere between baffled and delighted when I discovered that Bicester is pronounced "Bister".
there are many examples of mechanical SLRs from the 60s that still work and require only about an hour of reading instructions and watching Youtube to restore to mint condition.

There are a ton of Asahi Pentax cameras that come with a classic 55mm Takumar lens for $20-30 on Yahoo Auctions (Japan) right now.
> The lack of effort to work with the rest of the kernel community.

It's not lack of effort. There's blame to be had on both sides, but for a long time (more than a decade) the kernel community stonewalled any security ideas because they just didn't care about mitigating unknown vulnerabilities. They thought it fine to just fix them after they're found, and have everyone recompile.

There's a few articles on this relationship, but it's not as one-sided as you seem to be saying.

The fact that it took order of a decade (I can't be bothered to look up actual years right now) between grsec adding non-executable pages to mainline Linux doing it is embarrassing.

The linux kernel community could and should have re-invented non-executable pages during that time, if nothing else, like when OpenBSD reinvented it and pretended they were first.
There is no "truth". There is only more-or-less likely untruth.
Washing machine, television, fridge, sure, 5 years minimum should be mandatory I think.

For smartphones I would stay at the current 2 years requirement though. A phone stays most of the time on a person, which is one of the most harsh conditions if you think about it.
I've worked with both, and let's agree that they are about equally hard to find, or more precisely hard to hire.

To the untrained, though, above average coders and managers may appear great. But only once you've met an actual great one, you can really have perspective.
Most distros have set KillUserProcesss to no for the short-term. Fedora plans to make all of the obvious user programs aware of the change (and able to create a new systemd unit for the process) and turn it back on for Fedora 26.

https://fedoraproject.org/wiki/Changes/KillUserProcesses_by_...

Their reasoning is pretty good, IMHO. It provides more control at low cost, and it's a one-line configuration change if you want the old behavior. But, everything I need it for (pretty much just screen and tmux) will already be aware and will handle setting up the new systemd unit automatically.
10 Famous Aррѕ Built with React Native