skysight-inc/HackerNews huggingface dataset:
A sense of shared sacrifice strengthens community bonds. I would suggest that there is a signalling problem that needs to be solved ("we are all in this together, making this sacrifice") - in other words, an unforgeable way for community members to signal to each other that they are not free riders. If everyone knows that everyone is not a free rider, the community will be much stronger. I submit that this is the primary reason religious "intentional communities" with strict rules are much more likely to succeed than the generic "utopian community" ones. Without that sense of shared sacrifice, it is too easy for grifters and free-riders to glom on.
It has higher energy density than Lithium, so theoretically yes it could increase the battery life of your phone. For equivalent energy the size is 33%, so one could fit 3x the energy capacity into a cell of the same size.
TLDR - things have names, isn't that terrible?
You can bound your loops and say you don't know. I thought that's what the parent meant by "don't know."
"Doctor, it hurts when I do this."

"So don't do it."

The problem with filenames is just a symptom of the biggest problem of UNIX conventions - passing around unstructured text. Filenames should have one well-defined format (AFAIR kernel allows pretty much anything but the NULL character). That's it. For most applications, filenames should be opaque data blobs compared for binary equality. But because we're passing around unstructured text, each program has to parse, reparse, and concatenate strings via ad-hoc, half-assed shotgun parsers. Each program does it slightly differently, hence the mess.
The point is GM won't beat Tesla, for similar reasons to why BB and Nokia didn't beat Apple, despite having a number of advantages.
> I usually use shampoo once every few weeks; I think the last time was in November but can't remember. Would be curious to see the trend over time.

You don't wash your hair with shampoo?
The OpenPOWER Saga Continues: Can You Get POWER Inside 1U?
I get the sentiment, but it really depends: For some services, it's very true. For other services, careful problem analysis will show that you only need one or two features from the full package, which then can be replaced by a very small shell script.
Who gets to decide what "accessible" means? Too many unix programs have their own completely ad-hoc printer and parser for config files, which have different assumptions. Some allow comma-separated entries in values. Some space or tabs are significant. Varying comment characters. Varying support for multi-line entries. Varying support for quoted strings. Varying support for unicode. Some are key/value, some are section based. Arbitrary special punctuation abounds.

It's a fundamental, unstandardized mess.

From the perspective of just a single program, then fine, it does what it needs to and its individual text formats are human-understandable, and its code is quickly banged together to do what it needs with it.

From an ecosystem perspective, it's a complete failure of usability and _interoperability_, which is the entire point of Unix philosophy in the first place!

Humans aren't the only ones reading & writing config files: Software needs to do it, too, be it applications or automation scripts. Again, text is a horrible substrate for compositing software functionality.
CPUs already have vector units. Having vector units that more closely resemble a GPU as part of the base ISA would be an interesting development.
Copying an .editorconfig in every new project solves any problems with remembering to use tab characters.
"docker" has too much brand recognition to let it go even though this whole 'rename' (that's what this is) makes things much more confusing than before.
kWh/kg would also make sense.
So we have a data point from four years ago and you are still harboring a resentment so hard that you feel you need to air your grievances for a completely different product. I get it. Hell hath no fury like a customer scorned.
I use Chrome. Here i can be sure to always have support for cutting-edge web standards, the developer tools are amazing and for anything else i have a great extension-ecosystem.
In regards to the last paragraph. If the type system is turing complete, then the type-correctness of the program _may_ be dependent on the output of an arbitrary turing machine. Therefore, your type checker must be either incomplete or its result must depend on the output of the arbitrary turing machine.
I definitely work more efficiently with people I can connect with. I think the bias is good.
Evolution does what evolution does. The problem is that selection pressure is too weak, and things that should die off survive and flourish.
I don't dispute that Javascript will be capable of it, or that there aren't ways of working around its limitations for modest scenes now. But I find it curious that you describe the problem as a matter of threading, as though throwing more cores at it is an appropriate solution.

Settings aside VR for a moment; the simple scene I described from cannon.js ought to be capable of being rendered in real-time, in software, at a smooth framerate on the machine I use. I believe this because I have decades-old software that can do this on that same hardware.

Shuffling the issue from improving Javascript's baseline performance to spreading the concern across multiple cores may improve the perceived experience for the user, but it comes at the expense of Watts and the overall amount of work that the computer is able to concurrently perform.

It's why in order to conserve power on my laptops I avoid launching the browser. The software trades battery life in exchange for overcoming baseline performance issues.
Default key bindings kind of suck...but actually pretty useable once you've gone and overwridden those.

Here's some of my overrides:

[
{ "keys": ["Ctrl+Enter"], "command": "copy" },
{ "keys": ["Shift+Enter"], "command": "rename" },
{ "keys": ["Ctrl+Shift+Enter"], "command": "move" },
{ "keys": ["Left"], "command": "go_up" },
{ "keys": ["Right"], "command": "open" },
{ "keys": ["Enter"], "command": "open" },
{ "keys": ["Alt+Enter"],"command":"open_with_editor"},
{ "keys": ["Ctrl+Alt+T"], "command": "open_terminal"},
{ "keys": ["Ctrl+Alt+Enter"], "command": "open_native_file_manager" }
]
I had 3 on a brand new macbook years ago and apple wouldn't take it back because it wasn't enough. they were very noticeable.
You probably can record quite a lot of that with your smartphone: GPS logging, sleep tracking apps, call/messaging logs. Even a basic calendar app can record specific mentionable events, but there are dedicated apps for that as well. (I don't do this myself, but know people who do this with varying intensity)
>But that would be true enough for they ran all of their own stuff, too... "Netflix is completely at the mercy of their ops team".

They employ their ops team and their ops team has equity stake in the company's success as well as their career riding on the line.

If a chunk of Amazon goes down and takes out your website, all you can do is wait and hope Amazon is prioritizing the fix.

>When Heroku went down, I sat around wishing it would come back up, and eventually it did.

This method of recovery just doesn't cut it in businesses with lots of transactions 24/7. Just sitting around can be flushing thousands per minute down the drain. In those deployments, you need to build across multiple cloud providers; and once you've reached that abstraction, you might as well have your own hardware as well and just burst to providers.

A company like Netflix can get by because they have their own hardware for streaming so an outage only affects people browsing for a movie at the time. And on top of that, their only interactive transaction is signing up for the service, which is extremely infrequent compared to the rest of the traffic. So essentially it's safe for Netflix to use AWS because they don't need high reliability/control of their own destiny.

>A small business with a single part-time developer can deploy an app to Heroku, and not need an ops person.

This use case I understand. However, anything at the scale that is frequently discussed in these contexts (gitlab, etc), they need ops people.
"Utilities" should not have to gracefully handle troublesome filenames, each one re-inventing the wheel.

If the system as designed accepts almost literally any characters in pathnames, it doesn't make a lot of sense to complain about people using "naughty" (troublesome) characters in pathnames they create.

It would have made a heck of a lot more sense to have disallowed stupid characters (all white space and control characters at a minimum) from the outset. However, changing it at this point is pretty impractical.

Of all the criticisms of UNIX, the singular one that strikes me as valid is the way that it accepts unquestioningly insane characters in pathnames. I would also maintain that case sensitivity in pathnames and a lot of other places is also a human interface error. It is arguable, and a matter of taste, but I find it obtuse. You should be able to "say" pathnames. The necessity for circumlocutions like "Big-M makefile" is offensive.

I'm one of the biggest fans there is of UNIX and C and the Bourne shell and derivatives, but recognition of weaknesses and flaws in those you love is not weakness; it is wisdom.
Thank you for adding this comment. I am glad there are more people out there that aren't afraid to be honest about some of the nonsense 'follow the process no matter what' stuff that I have experienced over the years.
Someone on your team is a talented designer and has built a beautiful site. Unfortunately, the scroll-jacking and large visuals take away from the UX side of things. Ask yourself which of those images clarifies your service and which distract from the message you are trying to communicate.

Oh, and change 'Our business model explained'. That language makes sense for startup junkies and business folk. But, has no place on your landing page, something like 'How we'll help you find a renter' is much more relevant to your audience.
This is great. I haven't delved into AI much yet, but what I've seen through 10 years as a language-learning specialist is that information and computational approaches to learning fail miserably in ESL, as does most schooling.

The brain is wetware. It's organic and grows into abilities through practice and use with proper modelling from an expert.

I get an itch to correct when I read AI discussions, as they usually assume information theory as fundamental to intelligence and mind.

Go try to learn something really hard, and pay attention to your internal process as youre doing it, then go and teach someone else that same skill and pay close attention to their process, while comparing it to what yoh went through to learn the skill you are now teaching. Then you'll have the substance necessary to theorize about the learning mind. Then again, me telling people who only deal in abstractions to go out and learn through concrete experiences is probably barking up the wrong tree.
if loopcount > limit then Left Dunno else Right ...
Hmmm, apparently 2016 and 365 support SVG finally?

https://support.office.com/en-us/article/Insert-SVG-images-i...

Only 17 years after the spec was established.
I don't know about paradoxical. But we know he shipped tech that was good enough.
> be thinking of racial slavery, which was inspired by a belief that other races were subhumans.

No, I'm not thinking of racial slavery. I'm thinking of slavery defined by Aristotle, whose view is representative of the classical world: "

"anyone who, while being human, is by nature not his own but of someone else…he is of someone else when, while being human, he is a piece of property; and a piece of property is a tool for action separate from its owner."

If this doesn't sound dehumanizing, I don't know what qualifies.

As stated before, a citizen of a state can renounce said citizen and emigrate to Bir Tawil or some other unclaimed territory. Unlike Aristotle's definition, you, by nature, are not of someone else and has the free will to choose to leave. That states have laws limiting absolute freedom does not equal slavery
SSRF is an extremely bad vulnerability; it's usually game-over on penetration tests. The zip-file path validation bug is also bad.

I'm pretty ambivalent about these "we got a security review, they said we're good" updates, even when they include the actual contents of the report (the final contents of the reports you actually see are almost always negotiated between the client and the testers).

It is a real problem for the industry that there's no clarity to be had about what it means to have had an assessment, what the different assessors capabilities are, how engagements are scoped, &c. I tend to mistrust organizations that use audit results to claim a clean bill of health --- or anything like that --- but more and more projects do that now, so I don't know how valuable that rule of thumb will remain.
>Sure, paying extra for a dynamically scalable service is inefficient if your resource needs are flat 24/7/365, but is that realistically the case?

Yes, the vast majority of apps are not 12 factor architectures designed for scaling so nodes can't be brought online and killed at the flip of a switch.
I bet to wager Netflix and Snapchat are at Facebook scale. Certainly $500M/ year in cloud commitments for the next 4 years seem to indicate so.
All the benchmarks I just glanced over show a different story. Yes, big games claim to want 4 cores because that's what big intel has offered for big gamers. Sure they run on 8-core chips and may get a speed boost for that, or not. But it is quite small overall, with the Intel 4-core parts mostly performing better than Ryzen while being cheaper or similarly priced as Ryzen.

What some people here are anticipating is the situation where games really do scale well to 8 cores, at which point we'd likely see the Ryzen compete against Intel's stupidly expensive 8-core parts and roughly match them in performance while solidly beating them in price/performance ratio. Just like in the encoding benchmarks that actually do run well with multiple cores. These games aren't here now. We aren't there now. But it might be the future.
If you get the same energy in 1/3 that space (but 2.5x the weight), you could have a phone that is the same size as today but with 3x the time on a single charge in exchange for a battery that is 7.5x heavier. Phones are light enough that I'd probably make that trade.
The way your blog looks like and by asking a question like that i would guess that you are pretty unexperienced. But this is gross estimation.

Of course you can be a good marketer, if you want to. Try to get as much experience as possible. Also "marketer" is a pretty big name. You should focus on certain disciplines at the beginning, master them and then move forward.

But the fact that you start by writing down/share your knowledge on a blog is a good mindset and beginning. ;) So keep going.
Newer memory uses smaller transitors which are more easily corrupted.
...I have just installed Minix 2 on my new laptop; a 386 with 1MB RAM, running at 16MHz, with a 80MB (with an M) hard drive.

In 16-bit mode, it runs beautifully (there's not quite enough RAM for the bigger 32-bit binaries). It's a pretty good Unix, with networking support, cut down versions of all the standard tools, it comes with full source and several toolchains making it almost completely self-hosted, and it'll rebuild its own kernel in 13 minutes.

It is beautiful. If you're interested in operating systems, definitely take a look. (There is a Minix 3, but I find it doesn't have the same minimalist charm.)

http://minix1.woodhull.com/
You could say the same about "mv". Move what? Files? File names? File parts? Users? Machines? Screens?

There's always some default subject implied for every command name. For "find" it is files, for "search" it could have been text.
APEX Expert Solutions LLC | Software Engineer | Northern Virginia | ONSITE | http://www.apexxs.com/apex-careers-2/
APEX Expert Solutions is a multi-discipline solutions provider headquartered in Arlington, VA. APEX tightly couples Analysts, Operators and Engineers to deliver mission success. APEX combines skilled engineers and developers with experienced intelligence analysts, to identify capability shortfalls and rapidly create tailored solutions with direct feedback from operators.

Join a small engineering team in a divers, rapid paced environment. We are looking for experienced developers to help deliver secure, reliable solutions to meet a wide range of technical challenges. Areas of expertise should include native Linux & Android development, static & dynamic security analysis, and firmware programing including device encryption and secure booting.

Must have an active SECRET Clearance, willingness to obtain SCI eligibility and CI polygraph
An interesting counterpoint:
Early Mormon settlements in western North America had a 90% success rate. In Utah, the success rate was 94%. [1]

Renowned urban planner Andrés Duany has praised the design of these communities. [2]

[1] https://youtu.be/5xP33zsNTzE?t=25m30s

[2] https://www.youtube.com/watch?v=58VW0ihf3SA
Ordered a 1U from them. Going on a month now with no delivery date yet and no indications there would be a problem until after we ordered. Not a big deal for us, we can wait and ordered it because it was cheap, but consider yourselves warned.
It was an OpenVMS derivative wiyh code copied or clean-slated against a modified form of its behavior. However, I heard the networking stack was from BSD.
No, because the packages are already signed with gpg. That way you can verify the checksum already.
Even more impressive (to my way of thinking) is c4:

https://github.com/rswier/c4/blob/master/c4.c

c4 is what you might call a microscopic C compiler; it's surprising how much it does for the code it has.
no, The age in the title make the story more interesting to me.
If this boils down to an engineer incorrectly entering a command can we please refer to this outage as "Fat Finger Tuesday"?
>What do you mean by this, because it sounds like a straight up lie?

There is no economy of scale with the cloud. As you scale up your service, Amazon/Google happily scale your bill right up with it. When you roll your own datacenter, things get much cheaper per unit (bandwidth, storage, etc) as you get larger.
For one, I read in an HN thread that Snapchat Android doesn't actually use the camera API for the phone, it just screenshots the screen.
This demands the question - why allow control characters in file names at all? Non-printing characters?
Interesting (sorry, I'm new to Linux packaging). So would it be safe then to replace by http? (Not that I'd take this at face value, but I am interested in your opinion)
XML, YAML, JSON and s-expressions are all just flavours of representing trees.

So yeah, any of that would be a much better idea than unstructured text, and yes, you can serialize all those use cases into trees. I'd steer away from XML for sake of efficiency and human-readability though.
Yes. Heaven help you if you have an extremely common firstname.lastname combination where there are multiple spellings of the first name.
Once you're in someone's address book, it's nearly impossible to get them to delete you if they're not tech-savvy. So every time someone intends to email Jon.Smith@gmail.com they send it to John.Smith instead.

There are companies that have been emailing me contracts for years now. I've gotten multiple divorce records, tax returns, all sorts of confidential information. I guess that's what all those legal disclaimers in the footer are for, because someone could do a ton of damage with the information I've gotten.
(May 2016)
Easy: a tool comes with it yo do that or it's a standard, data format you view with existing tool. You even get closer to UNIX philosophy of one app per task that way given the mess ad-hoc text leads to.
First, equity isn't compensation, it's ownership. Second, it's about risk. Third, it's about luck.

So, if you get paid a market salary and benefits, you can't really expect to own much of the company that's providing you with that salary and benefits as it's essentially burning money on you. If you came in and said "can I get 1% ownership if I take 15k a year with no benefits" that would be a different story, but that's not how this works.
Is Lambda only for workloads that require serverless architecture, or is it also for workloads for folks that would like to be running serverless?

I have a variety of web application APIs running on webservers in a VPC, with an RDS MySQL instance for backing. I'm interested in writing our new development using Lambda, but I'm still using MySQL as the database backend for now, and I still need to interact with existing APIs in the VPC. Perhaps someday I will have moved all those other applications to Lambda as well, and perhaps someday I will port all of our database functionality to DynamoDB, but I don't think that should be required in order to just get started with Lambda.

If I was writing everything from scratch, maybe I'd go full serverless. But I'm not in that case, and I'm also not in a case where MySQL won't "scale" for me at all (I wish I had that problem). If Lambda's not for me, any Amazon engineer can feel free to tell me so, but given their marketing, I did not think this was the case. They offered Lambda VPC for a reason, even though it doesn't work very well currently.
The big deal is on the http://www.anandtech.com/show/10353/investigating-cavium-thu... page: the MySQL transactions per watt is absymal compared to the Xeon D. Really, badly absymal. So... this is not a useful server. When someone says ARM I am thinking "low power" but this is a 120W CPU which is beaten by the 65W Xeon D-1581. Pass. Let me emphasize: very often I do not care about absolute performance numbers because your power budget is almost always limited in a data centre, what I care about is performance per watt. Which here the Xeon D wins. Like, big time. Tangentially: this is where Ryzen battle will be as well. I was crunching the numbers from http://images.anandtech.com/graphs/graph11170/85875.png and the Ryzen 1700 is only beaten in performance per watt by the i7 7700T and only by 5% while in performance for dollar the 1700 has a comfy advantage over every Intel CPU, 62% over the i7 7700T which is a lot to pay for a 5% advantage. This shows the Ryzen is practically on par with the i7 series: the 7700T is 4 cores in 35W, the 1700 is 8 cores in 65W and they are head-to-head. I want to see the 8 and 16 core Xeon D chips battle Naples but I am afraid AMD is simply not yet in the low wattage game. But I really would love to see some competition there!
What bothered me about running TrueTech is that customers would sometimes demand repercussions against employees for making mistakes.

Enter Frans Plugge. Whenever a customer would get into that mode we'd fire Frans. This was easy, simply because he didn't exist in the first place (his name was pulled from a skit by two Dutch comedians, bonus points if you know who and which skit).

This usually then caused the customer to recant on how he/she never meant for anybody to get fired...

It was a funny solution and we got away with it for years, for one because it was pretty rare to get customers that mad to begin with and for another because Frans never wrote any blog posts about it ;)

But I was always waiting for that call from the labor board
to ask why we fired someone for who there was no record of employment.
I'm not sure if you're serious or throwing some very excellent shade.
This is what I got frustrated with and decided to stop waiting & buy a Ryzen, in fact. I've been looking forward to an enthusiast segment desktop chip with eDRAM and Iris/Iris Pro (or better!) from Intel, for a few years now, but it hasn't surfaced.
Google "davec apcobj.c"; that'll point you in the direction of some of Dave's brilliant work that dates back to 1989.

(Three versions of NT have been leaked; NT 4.0, Windows 2000, an the Windows Research Kit (which is Win2k3) -- they are all trivial to find online (first page of Google results).)