skysight-inc/HackerNews huggingface dataset:
I'm late to the party, but here's why I need (well, want) more than 16GB:

Apps - some are large enough and used frequently enough that I don't want to have to do the download/delete cycle on them.

Photos - I went to Italy a few weeks ago with a group. One of the guys had a 16GB phone. He was emailing the photos to his wife each night and deleting them after because he didn't have enough space. That's annoying, and what do you do when you don't have a data connection and run out of space?

Music - sort of agree, but again, limited data connections do happen. Even when they don't, streaming saps the battery compared to playing already downloaded songs.

Books - I play tabletop RPGs, less now than I used to. But when I played more, being able to pull from my collection of books quickly (some of these are just scans from old books, 100MB for a manual). Having to download them off Dropbox each time, or download/delete cycle through them to make sure I had enough space, would be annoying.

Updates - an ex-girlfriend had the 16GB one when iOS 8 (?) came out. I kept telling her that we could update it on her laptop via iTunes and get around the problem, instead she cleared out a bunch of photos (and later regretted it because she was a dope and didn't back them up first) and apps (fewer regrets, those were just downloaded again) so she could download and install the OS update. AS I recall, that one had an absurdly large free space requirement, but even requiring a more modest 500MB-1GB of free space could be difficult to meet sometimes if you only have 16GB and downloaded music, apps, photos, videos. Which items do you delete to make room?

EDIT: I'll note, this is more of an issue for me on tablets than my phone. I have fewer big apps on the phone that I couldn't delete, and I never watch video other than streaming some youtube content if someone sends me a link. My tablet, on the other hand, is my go to device when traveling and gaming (a fair number of good board games have apps for iOS and the iPad, much easier than carrying around several boxes of boards and pieces and rules to play with friends).
Hell, a lot of the base docker images I've been using lately don't even come with netstat or vim on them.

I'm already feeling the "can't debug" pinch and we haven't even started getting into unikernels yet.
Although the determinate of that matrix = 0, and if it's conjugate transpose determinant is non zero then I wonder if all valid possible configurations on this board can be represented by a complex lie group?

Edit: did the work, it does, but too lazy to describe the group https://gist.github.com/cinquemb/18e494348045725e2b60
Hackers in SF or Nairobi
A Players Don’t Hire a Players – They Partner with a Players
A move that returns to a previous board position is illegal, AFAIK.

http://senseis.xmp.net/?TrompTaylorRules :
6. A turn is either a pass; or a move that doesn't repeat an earlier grid coloring
Yes, sorry for that. Don't hesitate to create an account on Framabag.org (it's free!) to test stable version.
It's a bit of a joke, but yes NY Times does a good job :)
> You won't find such a new language. Most languages in use are already known to be Turing-complete.

I beg to differ: http://tkatchev.bitbucket.org/tab/

(Sorry for the shameless self-promotion, but you're wrong that nothing new can be invented.)
1) Constituent services are at the heart of every local government and the data surrounding them are its vital signs.

From an operations (top-down) perspective, constituent services tell you which departments are living up to their civic mandate. Think CSAT and NPS in SaaS companies — two metrics that predict retention and growth, that measure how you're doing and customers' faith in your future.

If, bottoms-up, you want to drive democratic decision making with real data, look at the hundreds of millions of interactions constituents have with their local government. It's only by improving the day-to-day that governments get a high-level view of what structural changes need to be made.

The product focus of Romulus is on those day-to-day users right now, but it's really the level above — the chiefs of staff, elected officials, city managers — that love the potential.

YC) Will do. As a philosophy major, I'm glad to see more liberal arts around here.
Hi Michael and Aaron. Just a curious general entrepreneur question. If you had to name one uncommonly known success factor beyond the standard-fare hard work, baseline intelligence, persistence etc., that you immediately look for in other successful entrepreneurs, what would that be?
More than that I've noticed about 30 years of consistent and regular fluff pieces to glamorize people such as Bill Gates and Jeff Bezos. One of the notable exceptions is Steve Jobs who stopped giving interviews to these kinds of reporters in the 1980s, and also stopped getting covers around that time (after that, if he's on a cover he's holding a new product.)

One observable consequence of this is that Steve Jobs who gave us so much is widely reviled, while Bill Gates who destroyed the packaged software industry, almost killed the internet and went so far as to have schools raided by SWAT to make them buy windows licenses for their computers (computers that were Macs, by the way, back when Macs ran PowerPC and couldn't run windows anyway)... is widely regarded as a humanitarian[1]. Jeff Bezos (whom I've known personally) is widely regarded as a Tech guy (despite being really just a pointy haired boss.)

There's a reason these guys spend money on PR-- the PR becomes the public perception.

[1] I've been in the room when both Steve Jobs and Bill Gates and Jeff Bezos lost their cool (three separate occasions, fortunately I was not the target.) Steve was quietly upset "how are we going to fix this?" and "we're never going to let this happen again, are we?" with all the weight those comments imply. Bezos and Gates both lit into the person with a clear intention to make their victims feel like nothing (both in different ways brought up the victims family as well.) I worked at Amazon and Microsoft, but not Apple.
A Unix-to-HTML5-Canvas screencasting system
The issue GP talks about comes from the cost of context-switching on a syscall (going into "kernel mode", performing the call, then going back into "application mode"). There's no context switch in a unikernel.
Well, we we don't need any of the other stuff, if you just replace redux, etc with their equivalents in clojurescript!
Duplicate of: https://news.ycombinator.com/item?id=10913144

(also posted by nikolay, 6 days ago)
Andreas Osiander: The greatest villain in the history of science?
Writing is Nature's way of letting you know how sloppy your thinking is -- Guindon

From what I understand of MirageOS an impetus for the "security theatre," is that they believe libc itself is a vulnerability. Therefore no matter how secure their applications are they will always be vulnerable. They will be vulnerable to the host OS as well as any process it is running and the vulnerabilities they expose. It's not security by obscurity but a reduction in attack surface which is a well-known and encouraged tactic. I don't see any prepositional tautology there.

Yes they will still be reliant on Type-1 hypervisors... and Xen has had its share of vulnerabilities in the last year. That's a much smaller surface to worry about.

The other benefit is that jitsu could be one interesting avenue to further reduce the attack surface. Summoning a unikernel on-demand to service a single request has demonstrated to be plausible. Instead of leaving a long-running process running you have a highly-restricted machine summon your application process in an isolated unikernel for a few milliseconds before it's gone.

The kinds of architectures unikernels enable have yet to be fully explored. The ideas being explored by MirageOS are by no means new but they haven't been given serious consideration. They may not be "ready for production," yet but given some experimentation and formal specification it may yet prove fruitful.
I really do feel like at the end of this container experiment we're going to reinvent microkernels. Possibly badly, but I'm hopeful that it won't work out that way.
After registering, I receive an email:
- from webmaster@example.org
- named 'webmaster'
- subject 'Welcome OJFord'
- signed off 'Regards, The Team'

That is, it does not at all identify where it came from. The example.org sender is particularly odd, I don't know why you're doing that?
This is true and accurate. However, substantial ongoing investment in the US rail system in the past 5 decades or so has been mostly private or private-public-partnership.
"If this were true, and an issue, FPGAs would also be completely unusable in production."

BOOM! And kernels. And ASIC's. And so on. Yet, we have tools to debug all of them. But unikernels? Better off trying to build a quantum computer than something that difficult...
That's interesting! Ok so I'm guessing this is the crux of the "do things that don't scale" mantra. Thanks!
You mean by the end of January.
Sounds like it is time for the three of you to have an honest conversation about what you each want and whether or not you should be working together on a startup.

Hopefully like you've been friends long enough to get through the pain to the right answer and keep your friendship.
FTA: "If you want to reduce burn, the least painful thing to do is make a lot more money immediately. Hopefully you have been trying to do this anyway."
Was gonna say. But why? Just pure PR?
Personally, I wouldn't use unikernels for my custom app-tier code† (unless my app-tier either was Erlang, or had a framework providing all the same runtime infrastructure that Erlang's OTP does.)

Instead, unikernels seem to me to instead be a good way to harden high-quality, battle-tested server software. Of two main kinds:

• Long-running persistent-state servers that have their own management capabilities. For example, hardening Postgres (or Redis, or memcached) into a unikernel would be a great idea. A database server already cleans and maintains itself internally, and already offers "administration" facilities that completely moot OS-level interaction with the underlying hardware. (In fact, Postgres often requires you to avoid doing OS-level maintenance, because Postgres needs to manage changes on the box itself to be sure its own ACID guarantees are maintained. If the software has its own dedicated ops role—like a DBA—it's likely a perfect fit for unikernel-ification.)

• Entirely stateless network servers. Nginx would make a great unikernel, as would Tor, as would Bind (in non-authoritative mode), as would OpenVPN. This kind of software can be harshly killed+restarted whenever it gets wedged; errors are almost never correlated/clustered; and error rates are low enough (below the statistical noise-floor where the problem may as well have been a cosmic ray flipping bits of memory) that you can just dust your hands of the responsibility for the few bugs that do occur (unless you're operating at Facebook/Google scale.) This is the same sort of software that currently works great containerized.

---

† The best solution for your custom app-tier, if you really want to go the unikernels-for-everything route, might be a hybrid approach. If you run your app in both unikernel-image, and OS-process-on-a-Linux-VM-image setups, you'll get automatic instrumentation "for free" from the Linux-process instances, and production-level performance+security from the unikernel instances. You could effectively think of the Linux-process images as being your "debug build."

Two ways of deploying such hybrid releases come to mind:

• Create cluster-pools consisting of nodes from both builds and load-balance between them. Any problems that happen should eventually happen on an instrumented (OS-process) node. This still requires you to maintain Linux VMs in production, though.

• Create a beta program for your service. Run the Linux-process images on the "beta production" environment, and the unikernel-images on the "stable production" environment. Beta users (a self-selected group) will be interacting with your new code and hopefully making it fall down in a place where it's still instrumented; paying customers will be working with a black-box system that—hopefully—most of the faults will have been worked out of. Weird things that happen in stable can be investigated (for a stateful app) by mirroring the state to the beta environment, or (for a stateless app) by accessing the data that causes the weird behavior through the beta frontend.
China company VCG acquires rights to Corbis, Getty images
No I don't. UTC.
> With unikernels you get a lot more consistency

That's not unique to unikernels. You can get that with Docker containers or EC2 instances on AWS.
I think this article needs to be paired with an article about "When to shut your company down." If I recall, that article exists and it basically says: when you lose hope.

Maybe I am not looking at this right but this part doesn't make sense to me:

In many cases, <2 months is the point of no return. If you are in this state it is immediately necessary to lay off your employees and give them severance, pay down your obligations, and use your remaining cash for shutdown costs.

So is that for companies that had a year+ of runway at some point and are now down to 2 months? What about companies that never had 1 year of runway? The differences between those are pretty big.

For example if you have a 4 person startup and 2 months of runway after being on the market for only 4-6 months, you are supposed to just shut it down?

No, you take consulting jobs and do side work till you can get higher revenue or some financing.

I think, like most startup articles, this applies to companies who have already gotten past seed stage, initial traction and thus is not applicable for 90% of us.
Some times the moderators offer people to repost interesting stories that have not gotten that much attention.
Reasons for Judgment released by the Ontario Court of Justice:

https://www.canlii.org/en/on/oncj/doc/2016/2016oncj35/2016on...
Ex. A user wants to try it out but paying for a custom domain scares them. They stick to a free subdomain, but never really promote it since it conflicts with their own branding.

Admittedly you're making a good point here that users _would_ get more value this way through increased branding.
Im Co-author of Xenon. We use it for our public and internal projects both angular and react. We use it for Searchkit!

Love to hear your thoughts on the project.
I'm happy for this article because it does hit some points on the head. Other points are deeply entrenched in Bryan's biases, but I can't really fault him for that.

In particular, I am suspicious of the idea that unikernels are more secure. Linux containers make the application secure in several ways that neither unikernels nor hypervisors can really protect from. Point being a unikernel (as defined) can do anything it wishes to on the hardware. There is no principle of least-privilege. There are no unprivileged users unless you write them into the code. It's the same reason why containers are more secure than VMs.

Users are only now, and slowly, starting to understand the idea that containers can be more secure than a VM. False perspectives and promises of unikernel security only conflate this issue.

That said, I do think the problems with unikernels might eventually go away as they evolve. Libraries such as Capsicum could help, for instance. Language-specific or unikernel-as-a-vm might help. Frameworks to build secure unikernels will help. Whatever the case, the problems we have today are not solved or ready for protection -- yet.

This blog post was clearly spurred by the acquisition made by Docker (of which I am alumnus). I think it's a good move for them to be ahead of the technology, despite the immediate limitations of the approach.
The standard model isn't the same thing as quantum theory. It's possible to make a quantum theory of gravity that for one reason or another isn't compatible with the standard model.

More specifically, the SM is a theory of a bunch of fields plus a bunch of parameters describing how they interact with each other. Quantum mechanics is much more basic. There is an analogy (from Scott Aaronson I think) that quantum mechanics and classical mechanics are like two different operating systems, and the dynamical theories of physics (e.g. field theories) are programs that run on those operating systems. There are rules of thumb for porting programs from one OS to the other, but they aren't guaranteed to work.
Didn't a Stanford student already do this, posting XML of all federal/state judge opinions on his blog?

https://news.ycombinator.com/item?id=7026960 (discussion)

https://law.resource.org/pub/us/case/ (free mirror, looks like)

It's a great concept, and more/newer is better, but it seems odd for Harvard to act like they're the first to pull it off.
I am not criticising you - I am criticising myself for not making these criteria more explicit. If I had better explained what I meant by 1 for example then you would not have thought that your idea was bootstrapable.

Good luck with the diploma.
Yup, forgot pass-pass!
SSH backdoor found in even more Fortinet products
interesting take. I'd like to hear what PG and others think. Coming from a middle class background, I can relate a bit and see-observationally-the other components to what Ricky's calling "mindset inequality". It's almost like "new money" vs folks that have bigger dollars to spend growing up. I know a lot of friends that have deeply entrenched psychological elements they need to overcome before reaching that "next level" that were engrained because of their upbringing. And, to Ricky's post, it's sometimes more of a challenge than the monetary differentials.
iOS 9.2 Cydia Install – iOS Jailbreak Tools and Jailbreak Guide
Not only was it used in production, from the first-hand anecdotal accounts I've heard, the VAX/VMSclusters were near-z/OS level of reliability. For a brief time, it was used both in mission-critical environments as well as in academic institutions (basically two of the three large markets that existed during that era).

Every 10 years, the same thing gets re-invented. Take network block devices/clustered sharing. VMS had high-availability and each node you joined could use it's local disk as an aggregate resource. In the 90s you had AndrewFS and CODA (CMU's golden age IMO). Then Linux had the whole DRDB era which gained traction about 10 years ago right around the time Hadoop was gaining traction. OpenStack has Cinder. 10 years from now we'll have something else.

Anyways, great points and good post. VAXstations are available on ebay for pretty cheap, but I'd personally go with a hobbyist OpenVMS Alpha license running on ES40. I threw a setup together a few years back and it was neat. Thanks for the data-sheet, my father will get a huge kick out of it.
Did anyone get a push notification for this?
http://www.local10.com/news/police-officer-shot-miami-garden...
m:n does not an erlang make though (witness Go), and Rust was not headed in that direction.
Can they clearly communicate what they are working on in 2 sentences in a way that any parent would understand? Do they believe the measurement and testing?
I don't know why, I know that the rain/cloud animation is really CPU-intensive so it might be cached? Do you mind testing the same for /documentation where there's no animation, please?
"But NI will compensate lost development time with free hardware so companies love it."

WOW! I never even thought about that business angle to dealing with shoddy tech. Thanks for the warnings.

"Well yes. We're not exactly concerned with verification of the asynchronous system. Just making sure everything happens in the right order, and each thread is actually doing what its commended to do."

Glad you at least have an easy approach to dealing with that nonsense. :)
Looks great, any reason why CMD-Q doesn't work for quitting the application?
Loops are usually disallowed intentionally in this sort of thing, the so-called "superko" rule.
But what is better? Even outside of it?

If you don't know the answer to that question, then you are in no position to draw sweeping false dichotomies and grand proclamations as you did above. I have no interest in being your history teacher. I've posted plenty of papers on here, as has nickpsecurity here in the comments, and the link in my parent post provides a decent academic summary by one of the greats in the field.

(I'm not even sure if illumos can be described as "widespread" in any fair sense. In any event, being better than some relative competitors doesn't give one the carte blanche to be a pseudohistorian and denialist.)
There's an alternate approach that I was mentally contrasting with. You tend to see it with e.g. Ruby apps on Heroku: you can't "log into" a live app, but you can launch an IRB REPL—with all the app's dependencies loaded—in the context of the live app.

Having this ability to "futz around in prod" frequently obviates the need for prescient levels of logging. You can poke at the problem until it crashes for you.
Luboš is rather outwardly critical of loop quantum gravity, and since his blog is widely read, I imagine that's where most people get the idea that a lot of animosity exists between the two groups.
I didn't know of that, I'll surely try to contribute, thanks! (:
Also the BBC seems to have no link rot on their old articles http://news.bbc.co.uk/2/hi/uk_news/736080.stm
Yeah, I'm surprised more comments aren't pointing this out. To spell it out further:

> the number of valid positions [of a game on a 19 x 19 board] is 19 x 19 in base 3

This statement is true when replacing 19 with any number, since the number of legal and illegal configurations is exactly 3^(n*n).
Yes, we do currently have a bank account, though it is purely for the technology side - currently we are cash-only as far as orders/deliveries go. (We launched using Stripe, but they shut us down after about $30k or so flowed through our Stripe account - however, they were very sympathetic and wanted to work with us, but their hands were tied by their banking partners).

Currently we are in Sacramento only. We tried to launch briefly in San Francisco last year with a delivery service partner, but that fell through and we withdrew to focus on building/learning more in Sacramento before trying to scale out again - however, we were able to make over $16,000 in San Francisco in our first and only month with very little marketing.

The legal landscape is definitely still not where we'd like it to be, but in starting this company, I'm essentially placing a bet that the legal landscape will change in our favor in the very near future and that I'm getting in at exactly the right time (not so early where the business is unfeasible, but not too late where risk drops so low that too many big players get in the space...I was actually surprised that Eaze and Meadow popped up at the exact same time as I did). I think that the momentum that we see across the country is definitely promising.

The most interesting thing is that, delivery in Sacramento itself is technically illegal - however, it isn't enforced. I appeared on the top-3 news outlets last year stating exactly what I was going to do here, so if the City wanted to stop me, I definitely wasn't hiding from them. Since then, I've spoken with the city council, and am working with the vice-mayor of the city to work in a new law for delivery here in Sacramento.
>there would be a paper trail that a certain individual was targeted and records pulled.

I expected this too, and I was quite surprised to hear the us government had no idea exactly what Snowden had stolen. Kinda sheds light on the "protections" they have in place, in that they didn't seem to be very good at what they're supposed to do.
On a box that does a few specific things, you don't need to install updates.