skysight-inc/HackerNews huggingface dataset:
Other things that SASS does well at:

* Wrapping up vendor specific properties. Put all of them into a mixin, use arguments for the value and any edge cases, be sure that all vendors are covered properly at each usage site.

* @media directives in SASS can be used inside a style definition.[1] IME this makes heavy use of media sensitive styling significantly easier to read/manage.

* Nested rules and nested properties[2] help to make your styling cleaner. If your html already has a very component-like structure nested rules can mimic that, which makes the overall design easier to manage.

A lot of the functionality of SASS is geared around reusing bits of styling. Much of what you can do with it could also be done with multiple classes, but that generally comes at the cost of a class explosion as you parcel out the differences.

It makes it easier to move more of the declaration of how your styling works into CSS itself, instead of the final styling being almost equal parts html (and classes) and CSS, with you as the developer/designer being responsible for remembering how all of the details fit together.

[1] http://sass-lang.com/documentation/file.SASS_REFERENCE.html#...

[2] http://sass-lang.com/documentation/file.SASS_REFERENCE.html#...
Tresorit offers free encrypted storage for spreading digital security
p, footer {
margin-bottom: 20px;
font-size: 14px;
line-height: 1.5;
}
footer { position: fixed; }
If enrolling your key in a PKI controlled by world governments seems like a good replacement for a bad private PKI, yes, by all means, pursue DNSSEC as an alternative.
How we replaced memos with software
Ask HN: "Like" buttons for blogs that respect privacy and ownership
I'd love to have something that allows readers to "thank" me for an article they've read, and I like what Svbtle and similar CMSes offer.

I don't want to use anything awful from the perspective of privacy and data ownership like Facebook, Google+, etc., but just something very simple that increments a number for each post in some kind of database stored somewhere to give me an idea of what people like, and to serve as a simple reward mechanism.

Have you rolled your own somewhere, or is there a service that is as simple and respectful of users as well as blog owners out there?
The Large Hadron Collider project costs us $1 billion annually?
Seems a lot like http://smarterer.com/, which in addition, has integration into some ATS systems.
Where is FM mentioned?
Me too. Superfluous knowledge to me, however. Could I have traded that learning time for something that was generally useful to me I'd have done so in a heartbeat. Dumbing this process down is an excellent direction.
> You would not need HTTPS on an internal network.

Oh, really?

http://www.washingtonpost.com/world/national-security/nsa-in...
If you restrict yourself to 64 bit systems, you can essentially go back to using OS threads with blocking I/O because the address space is so large. You can fit thousands of 2MB call stacks into the processes address space and rely on the OS and MMU to manage the memory.

The problem that created the whole non-blocking, async domain was the memory needed for the thread's call stacks. You don't have enough address space to place a bunch of 2MB call stacks for each thread, if you're handling tens of thousands of connections.
To be honest, I don't understand why manufacturers are still optimizing CPU performance instead of battery life. Who really needs a 4 or even 8-core mobile device?
Most people I know with a smartphone, barely make it through the day and I often see them charging their phones at work.

In my opinion, companies should follow Lenovo's lead and address battery life concerns. A phone like the P780, with a 4000mAh battery, is spec'd to last for 36 talking hours [1] and it can easily be used for 2-3 days without charging.

I don't believe it is directly commercialized in the US, but the price point is not far from this Motorola, as it can be acquired from China for around 230-250 USD (e.g. through aliexpress).

[1]: http://shop.lenovo.com/ae/en/smartphones/p-series/p780/
I disagree that there is only one sure thing, it is also certain that:

A or not A
You're diligently missing the point. Which numbers do you disagree with? What do you think the more appropriate number would be? Change the numbers and rerun the script, so you can see if your argument even matters. If it does, pursue the argument.

Stucchio didn't propose a magic python script that answers the question of whether we should a basic income or basic job. He simply proposed a tool for making the debate more concrete. The debate still happens. It just gets less stupid.
Better build quality and camera; similar specs and price
New company lets you rent out your car while you're gone at the airport
I understand your concerns, the problem is when they're all tied in to the same database, they aren't modular. Modular means I can change one app without being forced to change the others and that's not possible when all apps integrate through a database. An integration database is a massive global variable that kills all modularity.

> "When you have limited developer resources modular balls of mud (AKA big glob of Buckyballs - like the magnetic desk toy) with single login identity and shared well structured DB are far better and easier to maintain than a half dozen+ separate applications with differing architectural choices, languages, and abilities to integrate with each other."

Easier to maintain, yes, easier to grow and change and evolve, no.
IDC: Android At 80%+ Market Share, WP 3Q13 Shipments Up 156.0% YOY
Why shouldn't we be (optionally) cutting CAs out of this? They're already known to be a weak link in the chain.

How about they make it an option to put your own certificate chain in your DNS records, require DNSSEC and use pinning to cover the fact that the DNS server might get intermittently MITM'd?
Well, as someone who isn't a web design diva it makes them look like they have no idea what they're doing.

"Hey guys, listen to us about design, we can't even get basic things right!". That's the message I get.
An Entrepreneur Who Manufactures Entrepreneurs
If they want to get rid of the cliff...why not get rid of the cliff?

They could have the options vest linearly (maybe with a gap at the start). That way no day is better than any other for quitting to cash out
For me, the big value-add of CSS pre-processors is nested rules[1].

[1] http://lesscss.org/#-nested-rules
>> The problem with this model is that the company at liquidity event often rarely resembles the company during the early phases. As such, the employees which benefit the company the most during the early phases, and whose skills are most aligned to those phases will not be fairly rewarded if they make the (IMO, correct) decision to leave the company to make room for the right people at those later stages.

Your concerns make sense, but can't you mitigate this with larger or better equity grants to those employees? Valuing their past effort is easily achieved with bonuses (I realize this requires the company to actually do it, but the concept works).
Here's an option you haven't tried:

5. Use CodeKit[1] on the Mac, and similar tools for Windows.

I can't tell you which ones on Windows are the best but damn it sure is nice to just casually write SASS/LSSS and have it get compiled when you save it because the compiler's sitting there watching for file changes.

1: http://incident57.com/codekit/
2: https://www.google.com/search?client=safari&rls=en&q=codekit...
Dead people that is what is wrong with it.
EMD domains have lost most of their charm. Google's been giving them less and less preferential treatment over the past year. With a recent update some of my EMD sites took a big hit just for the EMD keyword - went from #1-#3 to second page.
I generally like the sound of this, although really what it amounts to is a single trigger on a liquidity event. The dynamic pool part is the interesting bit.

Things I like

- Aligns employee incentives strongly with founders/investors in terms of seeking an exit. Some people now just jump from company to company collecting equity.

- When a company can expect an employee to be around for awhile and vice-versa, both invest more in each other.

Some questions and concerns

- Not all companies are going to reach a liquidity event and thus it may disadvantage employees if they feel more locked
in to staying onboard in a situation with limited upside.

- This may prompt more job candidates to only join companies which are sure-bets, and hurt companies with that crazy idea.

- Such a deal would probably even out with current offers of equity because time is equal to money, but the increased amount of equity will be used as leverage to reduce salary.

- Acquiring companies are going to hate this with a passion as they rely on there being some vesting time left in order to keep acquired employees.

- Although perverse, the dynamic pool aspect might make the first 15 employees try to get the others to leave since the upside of doing so is high. Likewise, if the pool is a certain size, there might be some resentment if the company hires more people and reduces equity for everybody else.

- What is preventing the company from simply adding more people to this coveted pool once one leaves, reducing the advantages the first few had?
Definitely a cool hack, but I had to laugh out loud at "Excel-like syntax (formulas start with "=")". Apparently the grammar for an "excel-like" syntax is:

excel_like_expression ::= "=" javascript_expression
I think he was talking about the FM radio.
M:N threading has been a great idea in theory for at least twenty years, but during that whole time actually implementing it has always ended in tears. The unexpected blocking in I/O or page faults etc. always trips it up. That's why it works great for HPC, not so much elsewhere. There's far more "bang for the buck" in making 1:1 threading work better.
100 growth hacks in 100 days - day 3: Screenshot demo data
I can't wait -- this is going to change my life as profoundly as Wolfram Alpha.

How¸ you ask? Well, I'll just Alpha that for you...
If the employee isn't adding value that is >= to their compensation, there is always an incentive to fire them. The point of this is to encourage those providing a value greater than the value of the DSP to stick around.
I wish I could do that. Unfortunately I'm on Verizon. :(
My guess is if that's the case, and this device will be widespread and popular overseas, they will specifically target it.
We're definitely considering it.
Bitcoin is a little bit weird because it is a currency which (essentially) nothing is priced in.

So actual users of bitcoin-the-currency don't really care what the price of a bitcoin is, as long as it is stable enough for them to complete a transaction. They don't need to buy 1 or 0.1 or 10 bitcoins, they need to buy exactly $100 or $10 or $1000 of bitcoins to complete their transaction, and the actual price per bitcoin doesn't matter.
Trending top 5 Weird, Funny and sizzling news of this week
Background: The author of this proposal, Daniel Micay (a.k.a. strcat, a.k.a. thestinger), is the most prolific volunteer contributor to the Rust compiler [1], and is fairly obsessed with eliminating design hazards that could lead to Rust not being competitive with C++ in terms of performance. For example, he was the driving force behind Rust's recent widespread switch from internal iterators to external iterators, and wrote most of the external iterator libraries himself.

[1] https://github.com/mozilla/rust/graphs/contributors

EDIT: To whoever removed the [Rust-dev] annotation from the title of this submission, please put it back. It adds valuable context, and it's in the title of the page itself, so you're violating HN's naming policy by removing it.
Circular references are not really "prevented". Most browsers just stackoverflow after a couple of thousand calls. The code below try/catches that error and simply continues.
Goose Extractor--An Article Extractor That Just Works
Using Google BigQuery for Event Tracking
I no longer work at the company in question, but the plan was to displace SQL for the records that were being used in MongoDB, for mongo to become the authority. NOTE: this was for a classified ads site for cars. Financial and account transactions and data would remain in the dbms, but vehicle/listing records would have become mongo authoratative.

The transition was difficult because of the sheer number of systems that imported/updated listing records in the database... there wasn't yet a 100% certainty that all records were tagged on update properly, so that they could be re-exported to mongo... each day, all records were tagged ... took about 24 minutes to replicated the active listings (about 50K records), and we're not talking "Big Data" here, but performance was much better doing search/display queries against MongoDB.
> But I can't write C# in it.

Doesn't change what I wrote.

> Regeneration is a problem when you have lots of developer workstations, build agents and test machines to deploy the Sass stack to.

It's no more a problem than all the other stacks you have to deploy. And if you can't deploy any stacks, maybe that is the core problem.

> Nope but it's a real problem. Some of our guys don't do the web.

They won't be able to merge HTML, CSS or JS any more reliably than Sass or Less, why are they doing those merges? Do you also ask designers to merge WPF?
I wouldn't trust a random website with my login info
What India Can Teach The Rest Of The World About Living Well
Gekko. A bitcoin trading bot written in node.js
I made no such comparison and any such comparison is a red herring. Bill the businessman was ruthless and unethical and destroyed many a business via illegal means. Bill the philanthropist is a great man who's doing great things that I very much support. One does not negate the other. I can despise Bill the businessman and look up to Bill the philanthropist at the same time.
So work in the crappy big cities, making your decent pay. If you save enough, maybe you'll be able to live in the mountains for a while before you die, hopefully not spending the entire time regretting that you lived for money instead of what you actually wanted.
That might just be a GNex issue. I don't have any issues with Chrome on my phone (which is slightly faster than the GNex but has the same amount of RAM).
p, footer {
margin-bottom: 20px;
font-size: 14px;
line-height: 1.5;
}
footer {
position: fixed;
}

btw I'm totally pro less/sass, but that example sucked :p
PS4 first impressions
What's poisonous about it? It's the blunt truth. In stack ranking, you don't have to be the best employee, you just can't be in the bottom 15%. If you get laid off, it means you're in the bottom 15%. There's nothing poisonous about that assertion.

It's like they say about escaping a hungry bear, you don't have the be the fastest runner to survive, you just have to be the second slowest runner.
Is solar powered electrolysis that bad? You could have platforms with solar panels and tanks floating in the ocean and every so often come to harvest the hidrogen and oxygen.
Is this a stupid idea?
I would also like to comment on this topic while pimping my company.
When I was a contractor at a major bank, the standard was IE6, and movement towards IE8 was in progress (as Win7 was rolling out)... I don't know if they held at IE8 though, as most people I knew there have left, even the FTEs. It was an SPA that drove a lot of adoption/allowance to use Chrome/Firefox, so it may have well gone that direction since leaving.
Would like feedback on site
Any language where you can avoid curly braces is superior to those where you can't. (Really, it helps with my RSI :)

Of course if you have existing CSS it might make sense to use LESS / SCSS.
Not entirely. I kind of agree. I think I even posted a nearly identical comment once.

It would be nice if there were two kinds of connections. Encrypted unauth and encrypted auth. That seems strictly better than offering unencrypted connections. Your browser could still display the "wide open to attack" icon for encrypted unauth if you like.
I don't think customers soured on HTC because their phones weren't awesome but because of their shoddy support and updates. The HTC One is the best phone I've owned since their Nexus One (probably the best phone I EVER owned) but they are laggards in getting software updates out. They're smart enough now not to set deadlines they'll break but not setting deadlines is maybe not a great solution to the problem long term.
That's only true if you are doing it purely for the equity (which is a terribly idea).

Many startups will pay salaries that match (or almost-match) those of larger companies, but the work at a startup is likely to be much more interesting - you'll usually move faster and learn more than at a larger organisation.
Show the sauce, luke?
Use Python-like indents in C
First analysis of Wikileaks leak of TPP IPR text
A huge applause for Miguel, he's been laboring over this for such a long time and it's amazing to see the fruit of his passion and perseverance.
So they are not really free.
Are You Among the 14% Who Always Tell the Truth?
Even better, she does things that aren't pranks!

http://canidu.com/

Don't get me wrong. Taco Copter is an excellent prank, and both of the pranksters involved are worth keeping an eye on.

Especially if they can get into your home, laptop, or vehicle ;-)
> Nothing but trouble merging the stored output from the tooling if you are in a branchy development. Basically, merge the CSS, then run sass/less and check in the change. Too much friction on a large project, especially when it comes to a non-Sass/Less dude doing the merge.

What is your reason for merging this? Accept whichever set of changes you want then rebuild the generated css at the end. If you can swing it not committing generated CSS to development branches is the way to go, but that isn't always an option.

Another option is to push merging/building duties off to your CI server. Little weird but it keeps things consistently updated and provides a backstop against parser errors.
And it's only going to be £3000 a seat!!!

Excuse the sarcasm but Mathematica is unjustifiably expensive to be general purpose and ubiquitous and I'm sure any derivative or superior tool will be as well.
I am pretty sure....Here there is a similar story. http://susanpiver.com/2007/11/06/stories-ive-been-told/ , and there is anotherone here...http://www.topquartile.org/?page=BOK_Trust_Integrity or this one...http://forums.comicbookresources.com/archive/index.php/t-108...
How did the US lose the first Gulf War? I think Iraq was removed from Kuwait right?
since google started silently removing all the referrer removal options developers contributed to chromium over time, I've started to call it Google's Chromium open source project.
LG’s Curvy ‘Self-Healing’ Smartphone May Come to U.S.
A Guide to SaaS Metrics and Your Pricing Strategy: Eliminating Churn
This is the list that I track and follow today. Apologies for any duplicates or typos. It's just my scratch pad list.

Of course my company, Codenvy should be in the list, too.

Koding (funded)
CodeRun
Eclipse Orion & Eclipse OrionHub
Cloud9IDE
CodeNow
Nitrous.IO
CodeCube
ApplicationCraft
Adobe Brackets.io
UmbrellaSDK
Vaadin Arvue
TrackVia
DevUnity
Py I/O
Web2Py
Collide (GOOG)
FriendCo.de
WebStorm
Coffee.io
Cloudifier
SWIFT Edit - England
CodePen
JSFiddle
Dabblet
Pastebin.me
CSSDesk
jsdo.it
tinker
SQL Fiddle
Compilr
Codeanywhere.net (funded)
IDEOne
PythonAnywhere
Scalakata.com
ideone.com
onlinejavaide.com
Kalupa Magikai
Ninja-ide.org
Microsoft TouchDevelop
Notepad++
Codepen.io
cloudenvy
http://icecoder.net/
jackdb.com
codio.com
codebender.cc
PythonMonk
Hull.io
maqetta
Codebunk.com
thebinaryapp.com
editey.com
brainengine
http://www.crunchzilla.com/code-monster
codiad
goorm.io
Microsoft Visual Studio Online Monaco
I very much enjoyed the 2 logic classes I took through the philosophy department. My school used to offer an interdisciplinary major between Computer Science and Philosophy. Unfortunately not any more.
The title has changed, it used to read: "Netflix ditches Webkit and HTML5 to roll out new UI"

Which seems to imply they ditched it entirely.
Electrify a village in India - Help us Raise funds
Who needs a 4 core device? Android users.

Try getting an Android 4 device with 4 cores and 2 cores and compare them. The performance difference is stark. The 2 core devices feel very sluggish on Android 4.
Using the diva metaphor: why did theater owners suffer prima donnas and their attitude? Because they brought in the crowds. They'd move tickets.

It's ALA's willingness to experiment (even if the end result is suboptimal) that made people listen to them about web design.
Pinch: An Agile framework for lean startups
I'm impressed with Jason's posts. He seems to be methodically working through all the misconceptions of inexperienced founders. This is an important and subtle one. Investors assume that if they're hearing about you first from you, you can't be any good. If you were good, they'd already have heard about you, because you'd have found a way to get introduced to them by someone they trust.

Even if investors didn't start out with this bias, they'd soon learn it from experience.
Mustbin launches to organize life's vital information
The Seven Privacies. How many do you know?
When we talk of privacy online, it is easy to narrow the discussion to something that can be described as “anti-wiretapping”. But privacy is a much more diverse and important concept than that. In general, we can talk of seven different privacies, each important to our civil liberties from different angles.
IDS was only one example.

When technology evolves, we tend to break the things that we used to work around the limitations in the previous technologies.

There's a whole suite of technologies in security that rely on the idea that we can look at packets as they travel to figure out if anything malicious is going on - Intrusion Detection Systems, Data Loss/Leak Prevention, Deep Packet Inspection Firewalls, Web Content Filters, etc. Each of those systems relies on the ability to see the unencrypted traffic - to "spy" on users, as someone else so snarkily put it.

As SSL has become more prevalent, we have turned to (as someone else pointed out) terminating the encrypted traffic once it's on a "trusted" network so we can do that - but, if HTTP/2 is ONLY over SSL, there will be no "termination" - it will be encrypted from one end to the other.

That means that all of the traditional security technologies will be completely blind to anything that happens in that communication stream.

I wasn't bemoaning progress - I think this is a good step. But it's also a step toward a temporary lack of security as the organizations catch up. It's because the security industry is a trailing industry (by definition) - you can't build a product that fixes security issues until you know: a) what the issues are, and b) how to fix them.

So, for a while, the early adopters of HTTP/2 are going to fly without a net somewhat.

(FYI - this same set of discussion points applies to IPv6 adoption)
Google's Android Eclipses Apple to Become the MS-DOS of Our Time
Rogue US-Israeli cyberwar weapon 'infected Russian nuclear plant'
10 Graphs That Sum Up the Medical Student Debt Problem