skysight-inc/HackerNews huggingface dataset:
I just spent a few hours installing Debian Testing on a 2 year old macbook. If you start with a net install you are mostly on your own, but starting with one of the live cds makes it pretty useable from the start. I think the big difference between the two is installing proprietary drivers. Wireless works out of the box on Ubuntu, but I have to install linux-firmware-nonfree and another broadcom package to get WiFi working on Debian.

I just tell myself that the extra work I put into a Debian install makes me more knowledgable about how the system actually works.
It recorded an early flaming in the diatribe against Engar Dug: http://etcsl.orinst.ox.ac.uk/section5/tr5411.htm
Thank you for enumerating those downsides. Clearly I'd avoid statically linked software if I would have the option to use `apt-get install` to get that software.

But in the situation that a new version of the software is released, and I think it would benefit me right now, I'd trade all those downsides for being able to use that software right now than waiting to be included in my distro (like it happened to me with Gimp some years ago).

I'm plenty of memory, storage and bandwidth but not so much of time to compile it by hand.

I have to admit that this is just a workaround while we find a better software release and dependency management system.
The biggest issue I see is that the original tech didn't replace the underfill. As a result the PMIC would not have the same drop resistance as a factory installed chip.

I would expect anything sold as refurbished to meet the same spec as a new device, and this one absolutely doesn't. This includes mechanical specs, which would not be fully tested when smoke-testing a rework.
Best EXIF viewer for iPhone/iPad
Inflatable space habitats
How else can they keep visionaries out of these schools if they don't apply the same worn out restrictions?
It should be perfectly reasonable, it is just that within the infrastructure of projects like Debian and RHEL there are no mechanisms for a developer to assume responsibility for their own software. The disconnect of both behavior and authority in pushing new releases vs distributing new releases is a problem, particularly for user facing applications and collections like KDE or VLC.

Debian can, and should, freeze their software and provide support for what they package. But the developer should both be able to ask Debian to remove it, and to provide it themselves. But not in the traditional insanely bad and broken Windows "search the Internet for random binaries and use those" method. We have the capability, fairly easily, to provide a community repository that crosses distros and lets developers directly ship and update their own software, we just need to provide the capacity. Tech like appstream is how you enable it.
By stated reasons I meant the politicians' reasons, like WMDs or hating our freedom. Sorry if that wasn't clear.
I spent a lot of time messing around with doing something similar and not succeeding[1].

I wanted to do full-on decomposed 3-point estimates. Which means representing something that is not quite a tree and not quite a table. Turned out to be harder than I was smart. I got the underlying calculation code to work fine, but never worked out how to get HTML to play along.

I did find reading about estimation to be quite enlightening though. My suspicion is that most of the improvement seen in 3-point estimates comes from decomposing the elements, not from the PERT formula.

[1] http://confidest.com
You're not the only one. Recently, I decided to try Fedora, though. It seems to work very well. However, I'm somewhat uncomfortable with it. I guess Red Hat makes a living selling Linux support, which means it's probably in their interest to make things unnecessarily complex. I'm not an expert but I looked a bit at SELinux (which comes with Fedora) and it seems rather complex. Then there's Systemd etc.
That does work really well for me in my Javascript code.

Java is getting increasingly painful to look at (even without operator overloading), and most of our work is still Java (due to the need to write so much of it???)
Or the other standby: take the dev estimate, double it, and increase the order of magnitude:

Dev Estimate Quote
------------ -----------------
2 hours 4 days
1 day 2 weeks

etc...
Very good points. I guess I've just been too lazy to learn advanced rebasing / commit aggregation. Maybe I should, so I can more effectively take advantage of the upside while not polluting my commit history with intermediate crap.
Good advice to have someone who knows what they're doing show you how to deadlift and back squat. I read Starting Strength before I started, but I'm glad I didn't try to do it on my own.

I'm iffy on the barefoot running advice. If you're going to run barefoot, it's probably best to do it on a soft surface like a grass field. But, that will allow you to continue to heel strike, and worse, because your heel will sink further into the ground, may increase the stress on your achilles. I prefer to advise people to try to land quietly[1], since that usually equates with landing softly. Also, re: heel strike, see this:

http://well.blogs.nytimes.com/2016/02/10/why-we-get-running-...

[1] Part of the reason I no longer run with music. I want to listen, literally, to my body.
Nope. But thanks for the warning.
A toaster keyboard would be awesome if, like me, you have butter fingers.
C is still the king of speed.
Laptop size genetics lab for under $1K
Oh I was confused for a moment, thought that only counted for the "external" clipboard. Obviously not :(
Seems yesterdays April Fools joke from Razer wasn't that far fetched after all. Coincidence, but still.

http://www.razerzone.com/breadwinner
This is the sort of thing that the site guidelines ask you to send to us at hn@ycombinator.com.
They're both fine. Whether you prefer to rent furnished or unfurnished apartments is a matter of taste. Either way, you'll have it like you like it within a couple of months.
This comment and the comment you replied to, are probably the most useful things to be read on HN in a long time. ;)
I heard Fabrikam makes good toasters! Among thousands of other random things...
Interesting. The only thing I could find on the man page with CC change cursor color. How did you come upon this?
> Can we wait until they actually do or talk about doing something bad before making a stink about them doing bad things? This is kind of jumping at phantoms, and doing that too much will mean losing the ability to do it for real.

Are you talking about the privacy aspect i.e the device regularly phoning home and sending data here?
It took me way to long to get that it was a joke.
HoloLens is a derivative of Kinect. Kinect 1 (with the Xbox 360) was structured light. Kinect 2 (with the Xbox One) is time-of-flight. I'm not sure which tech the HoloLens uses (I don't think Microsoft has specified one way or another, and I didn't have an IR camera to look to see if it was emitting a pattern), but I'm assuming it's based on the newer tech, because my understanding is that time-of-flight systems can much better handle having multiple devices scanning the same space. HoloLens handled this situation very well; I've seen at least 8 devices all scanning the same area without getting confused.

It's all driven by the unit, btw; no need for markers or external illumination.
Thanks for making this, it's definitely useful and the UI is very clean.

Bug Report: If you enter a non-int value for one of the values it returns NaN. I.e. I entered 1.5 for a worst case estimate and it did that.
Yep, Daly City is pretty miserable climate wise. It'll often be covered in fog and cold in the middle of a summer day, while a few miles away it's sunny and warm. You also have to deal with mold and rust issues.

I've looked at apartments there a couple times, and while it's vastly more affordable than SF, the climate + distance outweighs the upsides (for me anyway).
There are countries in Europe like Italy, if I am not mistaken, where entry standards are practicly non-existent. Many people start these degrees and few finish due to natural selection.

Thus, no requirements is not a problem as long as people do not get their degrees by cheating and not acquiring actual knowledge. That is probably going to be easier to be done in online programmes though which may become a problem.
The funny thing is I have seen many more damaging errors caused by operator precedence / grouping, which continue running and doing the wrong thing, than by type mismatch errors, which blow up and stop.
I'm running an i7-6700k, on Windows 10 with the MSVC 2015 compiler, my results were
9592 primes between 0 and 100000
Time taken = 12.808
Without optimisations, and
9592 primes between 0 and 100000
Time taken = 10.853
with full optimisations. I would ahve thought it would have been much better.
without and with optimisations.
I suspect that -

If the service is easy enough to provide (this means not just ease of deployment but also up-time, maintenance, etc) while fitting into their margins without issue, it doesn't provide stickiness.

If the service is sufficiently complex to provide stickiness, they either need to charge for it, or it will likely eat heavily into their margins.

Neither of us know the specifics of Digital Ocean's business plan, but I strongly suspect that were it as simple as you put it, where it's hardly any cost to them, and a huge gain due to increased stickiness, they'd already be doing it, or be moving toward it. And they might be. However, if they aren't, then it's hardly a mystery as to why they're not providing such services.
see kickstarter at https://www.kickstarter.com/projects/339005690/bento-lab-a-d...
It is not native advertising.
I kind of see what you mean, but tmux and mosh are completely different things and have (almost?) completely different use cases. Mosh is replacement for ssh.

Without talking about the other huge benefits of tmux, mosh only helps (and was designed to) prevent disconnections and other inconveniences when your internet connection falters. If for example your terminal unexpectedly closes you can't reconnect to your ongoing mosh session (this is an intended feature for security reasons).

Tmux on the other hand wouldn't help against a poor internet connection, but at least if your terminal or your ssh session closes you can just restart another one and wouldn't lose anything.

In other words, always use tmux, and tmux+mosh if your internet connection is poor.
It is wasting a lot of time with the pointless bool assignments. See my post below.
Just spent 5 minutes playing with it, looks very nice .. I especially like the visual cues about what is and isn't editable, and the whole app flows pretty nicely .. will come back and have another 5 minutes play with it in a month or so, in case you're going to push things forward .. I'd love to see some graphics in there, rendering the time-range data and showing relevant gravity between them, somehow, akin to some sort of waterdrop diagram .. anyway, good stuff, well done.
Weren't they bought out by Contoso?
Swifty D3.js: Part 1
I've talked with the Mill folks, and while I find their architecture intellectually/academically interesting, I just don't think that stack machines will ever take off. We've stuck to the tried and true von Neumann, while dramatically increasing memory bandwidth within a core, throughout a chip, and when connecting multiple chips, along with enforcing strict determinism at a hardware level, which is why our compilers work. We have one ACM paper published that is intentionally vague, but describes at a high level our scratchpad (software managed) memory techniques... we'll be talking the specifics of our full toolchain later this summer when we have a full public unveiling of the architecture.

Another problem with Mill is that they have been around for a little over 10 years, and have not released anything publicly (though have given a number of very detailed talks). They have had a lot of trouble getting their design into FPGAs, and even more trouble with having working compilers. When I started REX, I believed in getting it into silicon as fast as possible, as that is the point when people would take us seriously. We closed funding in July of 2015, and are taping out our first silicon next month... While many have called us crazy (and we will be giving real information on why we are not that crazy), I definitely don't want to be called vaporware.
Lisp doesn't prevent you from sequentially assigning expressions to symbols, rather than "infinitely" nesting stuff.

I suppose what you said is an "occupational hazard", but not an unavoidable problem.
I think civility is how we react to things that are different from us. In resolving conflict, we can bomb the shit out of each other, or we can greet our enemy with political statements. Both are painful but dead is an absorbing state, as long as you are alive, you can whine, rant or smile etc. Once you are dead, it's irrevokable.

Hence bombing is less civil on that ground.
Interesting. C++ and Java are very near on my machine:

java Prime
9592 primes between 0 and 100000
Time taken = 18.484
9592 primes between 0 and 100000
Time taken = 18.25
9592 primes between 0 and 100000
Time taken = 18.087
...

C++: https://news.ycombinator.com/item?id=11412820
They missed the Thompson-Ramo-Woolridge 530, which was the first machine with microcode in main memory. They called the microprogram words "logands", for "logic operands", and there was an logand assembler, in case someone wanted to write new microcode. This was a major milestone in microprogrammability. Or it would have been, if the machine worked.

The TRW-530 was supposed to compete with the IBM 1401, but the 530 was so unreliable that only two were made. Case Tech (now CWRU) got stuck with one years after it was discontinued. It was used only to copy UNIVAC tapes to IBM tapes as part of a migration to new UNIVAC hardware. The machine at least had decent tape drives. A custom interface connected it to a UNIVAC 1107, as a total slave of the reliable 1107. The machine was so cost-reduced that they didn't have buttons on the front panel; the operator used a "magic wand" (a logic probe) to touch contacts to set bits in registers.

Everybody involved in keeping it running was happy when all tapes had been converted and it could be sent off to the scrap heap.

The microcode in main memory idea came from an era when CPUs were slower than memory. Today, we need three levels of caches to deal with CPUs orders of magnitude faster than main memory accesses. But it wasn't until the 1980s that mainstream CPUs decisively pulled ahead of main memory on speed. In the 1960s, memory was waiting for the CPU, not the other way round.

This led to some strange dependencies on memory. The IBM 1620 had a base 10 multiplication table in main memory, loaded at boot time. That was how multiply worked.

Many architectural decisions in the history of computing came from the speed and cost of main memory. Virtual memory was developed as a cost-saving measure, to allow faking more memory by paging stuff out to disk. Paging out to disk is obsolete today (unknown on mobile, painful on desktops, dumb on servers) although most major OSs still support it.
This time around we have a decade plus of virtualization experience and specialized silicon in many (most?) modern processors like Intel VT-i/x/d and AMD-V. We no longer have to try to emulate kernel code or implement interfaces like POSIX or WINE on top of other kernels that inevitably lead to impedance mismatches between very different archirectures.

For example, modern virtual machine software like Parallels and VMWare Workstation allow for "unity" modes where the guest OS window manager is hijacked so that each window can be rendered onto the host without the rest of the guest desktop interface. If you're running the guest kernel "side by side" with the host as a virtual machine, you can focus on drivers that bridge the two operating systems (filesystem, network, window manager, etc.) and make it seamless instead of trying to shoehorn a low level emulated interface into a system that may not be ergonomic for that task.
Nintendo’s first mobile app is a Kafkaesque exercise in madness
Good to hear from someone who's actually been there, rather than the rest of us carping from the sidelines; but I have to take issue with

To do that you need to prove that you are there to govern, that means deploying troops/police in massive numbers and a court system that works

Is the US actually able to deliver a police and court system that works and has popular support in the US? After all, this is what the BLM protests are about.

The problem is made worse by the presence of factions in Iraq that would want Sharia law; there may be no set of law that's amenable to both the occupiers and the occupied.

(This went wrong very early on in Iraq, where the US overthrew the hated administration with its torture and secret prisons and installed their own torture and secret prisons instead.)
The issue is that Apple is trying to make it impossible for independent repair shops to buy the components (proprietary ICs and such) they need to fix the boards. Here's a video by someone who fixes Apple laptops for a living: https://www.youtube.com/watch?v=YcuAF3OJIoU
> What's different this time?

Running 64bit Linux elf binaries on the NT kernel, side-by-side with windows binaries is quite different from WSUS -- at least what experience I had with WSUS. It's more like Wine (a port of the win32 api to Linux (and BSD/OS X?) that allows running unmodified windows executables on Linux.

Being able to "apt install redis" on windows, and get the redis-build that Ubuntu ships, and be able to use it locally is a pretty big deal, IMNHO.
Now they only need their subsurface scattering to get better. Despite a lots of improvements it still looks like plastic.
Is it now?

This "safe" war is producing millions of refugees in neighbouring countries further destabilising that region. A good many of them headed and will continue to head for Europe with likely negative political and economical effects ranging from rise of far right, rising resentment between countries and growing wish to opt out of EU which however faulty its implementation doubtlessly is, almost certainly made continent more stable.

USA may not be affected at first degree, but since this is a fairly well off market of 500 million souls, crashing it would screw everyone.

(Also, I find expectations on how Syrians would read USA involvement just wishful thinking)
Don't get me wrong I also have a 2600K and have been somewhat disappointing with Intel's progress. But, for most workloads the current generation really is significantly faster.

PS: That's an impressive OC, I capped out at 4.2Ghz with air cooling, then pulled it back down to 4.0 for extra safety margin.
As well as the point made by the others, part of why he opposed (big C) Communism was that they were counterrevolutionary and suppressed the actual socialist revolution that was happening in Spain at the time. In short, the Stalinists were too right-wing for him. Homage to Catalonia does make that clear.

There's no sense, in any of Orwell's later writing, that he renounced socialism and plenty that affirmed his socialist ideas. Orwell stated in one of those works (Why I Write, 1946), that every word he wrote since 1936 was for democratic socialism, and the ending of Animal Farm, for instance, ultimately shows the communist pigs being no different from the capitalist humans (something that the CIA latched onto when they financed the 1948 animated film version, and so they had the ending changed).
Even though I am not a big fan of some of Go's design decisions, this is one area where I do say that Go is a real systems programming language specially since 1.6, regardless of what C guys say.

You have OSes written in Lisp, Cedar, Modula-2+, Modula-3, Oberon, Oberon-2, Active Oberon, Component Pascal, Sing#, System C#,...

All systems programming languages which do have a GC for heap management.

Given that the Go compiler and runtime are written in Go, with the necessary Assembly glue code, I would say Go is no less systems programming language than those referred above.

Even ANSI C, cannot be fully implemented without Assembly or compiler specific extensions for hardware integration.

But of course the naysayers will only change their discourse the day someone decides to invest their time and produce a bare metal runtime for Go, following the approach of one of those OSes that I mentioned.
I've run production at a 'successful startup,' a million node corporate fleet, and a personal toy project or six, and consider Kubernetes the single most important work being done in the field right now. Docker, no (rkt is better architected). Kubernetes, yes[0].

Don't think of Kubernetes as a replacement for Puppet. Think of it as distributed init/supervisord with service discovery, which you are clumsily building with Puppet. Your automation ends up writing init, units, monit, supervisor, and so on, right? (You shouldn't be deploying apps with Puppet anyway because CD is not CM, but nothing like Kubernetes or Mesos really existed in the open source world until now so a whole generation learned to do it with Puppet.)

Kubernetes exists for when your scripted machine fails or you exceed the capacity of your scripted machine and need to horizontally scale. It is not a deployment tool per se; that's only part of what it does as a scheduler and resource manager. Every project, from personal to Fortune 500, needs to plan for those scenarios. I'm not saying Kubernetes is always the answer, I'm saying it solves a problem that every project universally has, despite your claims. The bonus of working that way is now you have an API to your machines and can treat them as a single unit of resources. Kubernetes is about half of building your own mini Heroku.

You've heard snowflakes versus cattle, right? Your way is for snowflakes. Kubernetes is for cattle. The threshold where one becomes more productive than the other is the constant debate, and as an SRE, my opinion bucks must people who talk about this on where that threshold lies. If you self-identify as a sysadmin you'll likely have one opinion, devops another, and then you have my group of crazies that generally want to crush all snowflakes. I can speak with experience that our crazy SRE ways scale pretty well to the hundreds of thousands of nodes case but also work quite well for toy systems.

Subscribe to everything CoreOS is doing. There's a spectrum of quality there, but they're running with the programmable infrastructure ideal and have largely bet the company on the Kubernetes ecosystem.

[0]: Kubernetes makes some interesting choices versus Borg and I think they're going to have trouble scaling it to that, and Borg really shines at Google because of the global filesystem layer that exists on every machine (they don't realize this and are doing gymnastics around storage in the open source side), but if they can mature Kubernetes it'll be a solid building block for platform development and eliminate a lot of the clumsy scripts and automation that you are defending and push us toward programmable infrastructure.
Long and frequent deployments of reservists is a recipe for disaster. Source: am a former Army Reservist.
Hey Harish, thanks for your talk at the March London Django Meetup.

I'm starting to play around with Google Container service as you suggested, having a good time.
Execution in the Kingdom of Nouns(2006)