skysight-inc/HackerNews huggingface dataset:
It doesn't matter what is standard at most companies, you just do it. It'll work fine unless you have a taskmaster looking over your shoulder the entire time you're at work, or a micromanager who demands that you account for your time in hourly increments. And if those things are true then you should quite for reasons.
Maybe the ".invalid" [0] top domain would have been appropriate here.

[0] https://en.wikipedia.org/wiki/.invalid
That hasn't been my experience when working with or attempting to hire bootcamp grads, but I'm glad that it happens in some cases! I've seen a lot of HS-to-professional types, some with some college and some without.
I'm not an author in any sense that would cause me to use the service. It's just a role I find easy to imagine due to my daydreams. Ironically, in my profession many of my frustrations relate to people expecting free. I deal with them via hourly billing and retainers in my contracts.
actually - it was 14 000 transactions, but at 1400 different ATMs. stet
It's because of this bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1250947

Disable the box-shadow on .widewrapper.main and it works fine.
Oh, I see what you mean now. Thanks, I think you're right.
SCROLL JACK WARNING ARRGHGHHHHHGHHHHHHHH!!!!
Oh no, it's that box-shadow bug again :-(

We fixed in in Firefox 47, but the fix was deemed too risky to be uplifted to Firefox 46. That was probably a mistake. Anyway, Firefox 47 is going to be released in two weeks on June 7th. In the meantime you can remove the box-shadow from .widewrapper.main using the devtools, or you can use Firefox Beta (47) or Firefox Developer Edition (48), which you can get here: https://www.mozilla.org/en-US/firefox/channel/#developer
You get the same problem whenever you build up things piece by piece. So most often I work around this by atomically mv'ing a temporary file to the final product.

%.foo : %.bar
echo blubb >$@.tmp
cat $^ >$@.tmp
mv $@.tmp $@
They're probably Saudi or Gulf Arab tourists and not Turkish. At least, that was my experience when I have been to Turkey the last time and I'm from the region, I have an easy job identifying people's background from their accent, form and attire than outsiders.
Awesome... Its a great tool
Using JavaScript rarely seems to fix click-wait-click-wait. It just replaces the browsers spinner with a javascript spinner.

Raw HTML provides prefetch hints. That, combined with fast servers and replication to ensure those servers are near your users, are all a fast website needs.

Of course if your website is actually an app then maybe it shouldn't be a website to begin with.
I too miss GDS and its related offerings. Lately Windows built-in search has impressed me though.

I also had great hopes for nepomuk on KDE but I think that is discontinued now.
fair... but it's actually the CBC suite that generates the warning.
Java's SSL is very painful to deal with. It has no support for ALPN or NPN, making it really difficult to use for HTTP/2. Also, the GCM cipher suites are implemented in Java, not with Intrinsics, so they are painfully slow. As in 20MB/s. Openssl and Go's TLS get 3000MB/s for the same amount of CPU.

Worst of all, Oracle refuses to propagate patches backwards, so if you are running even a mildly old (like a year) JDK, you will suffer for it. Enterprise Java doesn't move that fast, so you end up having bootclass hacks to get around these shortcomings.

And oh yeah, if you also support Android, you might as well hire someone full time to deal with this, since it is that time consuming to deal with.
This isn't a Rails gripe. He only seems to know Ruby/Rails and lashes out at it. Frameworks = Lots of abstraction. At least the abstractions in Rails aren't leaky.
Hi! Needora is a reverse marketplace, it's focused on having people post what they need to buy, and sellers, rather than posting what they need to sell, they can proactively search if there is someone who already is needing their product.
Thanks for asking and let me know if you want more information. You can see this video to know more about needora: https://vimeo.com/167479865
Correct, there are a number of people that look at the actions of a contractor that exposed operational material and think - that's treason. There is a long history of Pentagon leaks regarding policy decisions (ex. shifting budgetary priorities or weapon system programs). However, to expose ongoing operational details - literally in the correct sense of the word - risks lives. Lives, assets and sources which he was willfully indifferent to. Not exactly the work of a patriot, as he likes to self-identify.
PageCloud (2015)
That's a totally valid point, but is 100% orthogonal to what's being discussed. Invoking a single command to validate, run callbacks, persist to the database, etc, etc. a model (and the larger argument of whether conflating DB access and persistence logic is a good thing) has nothing to do with whether the object is aware of it's own properties.

They are both critcisms of ActiveRecord, for sure, but quite a bit different in content. One (AR objects not knowing their own properties) feels, at least to me, like an unfortunate early design decision, while the other (encapsulating everything involved with saving a model in a single statement, "magic avoidance" be damned) is very much in line with the core philosophy of ActiveRecord and Rails.
In Java's defense its TLS stack and frameworks using it have grown organically over 20 years. Let's see how Go is doing with consistency in 2030.
A headscarf obscures the face, not unlike a surgical mask. What exactly are you correcting the record on?
Thx foz, I've experienced exactly the same. Furthermore this approach isnt just leaner but as the both teammembers at customer and partner side also focus at the social fit. In my opinion this got lost with the classic rfp approach, but is as similar important if your partnership will fund at agile principles
Looks like a great utility, but the output css isn't very compact. For example,

ul li:nth-child(1) {
background: red
}

ul li:nth-child(2) {
background: red
}

ul li:nth-child(3) {
background: red
}

should just be

ul li:nth-child(1),
ul li:nth-child(2),
ul li:nth-child(3) {
background: red
}

Also, it's not very clear how to download the family.scss file, it's buried deep in an oddly named subfolder in the repo.
solnic wrote the majority of DataMapper, its successor rom-rb, and the Virtus object modeling library. He knows much more than Rails and understands its problems.
"What is the best way to structure this so I can keep the most money e.g. freelance, employee, under the table, etc.?"

Definitely don't suggest to them that they should pay you "under the table" (i.e., off the books payments that are not reported to the IRS). That would be asking them to enter into a conspiracy with you to commit tax evasion, which is a federal crime. No legitimate company would do that, or want to deal with somebody who would suggest that they do that.
It's not hiding anything, other than the conventions. Django's spammy boilerplate is just default behavior.
> a single object or an entire object graph must be stored in the database

Hence "the last point" (though you might have caught me mid-edit). I view these as functionally the same problem: not only are you instantiating the object, but it must immediately go to live in the database or it's useless.

But you're right in that it is a philosophical problem. Rails is wrong. =)
This is about stolen credit cards. What do vulnarabilties have to do with it?
Who am I supposed to be rooting for in the article?

Besides the title nowhere do they make mention of this commercially available kit, it reads as DARPA is looking for ideas from people on how to make improvised devices from commercially available materials, I presume this is in effort to provide metrics to track and counter measures.
All the CBC suites in TLS are vulnerable to Lucky 13.
How the West Got Rich
> Are there any people not in favor of pardoning Snowden here?

Tptacek says that if he were president, he'd "see Snowden prosecuted for overtly and recklessly breaking the law, but would commute his sentence" ( https://news.ycombinator.com/item?id=5868853#up_5869346 ), whatever that means.

Marc Andreesen called him a traitor in a TV interview right after the leaks.

Even on HN and in Silicon Valley, there are people who think mass surveillance is more or less acceptable, even done in secret without the consent of the public, and that Snowden was wrong for revealing it.
I personally can't wait for Rails to be a distant past. So many start-ups got burnt badly by using Rails -- easy to start, hard to scale, maintain, and extend. Rails is too opinionated and if your use-cases don't fit into "Rails way" your screwed.
I'm somewhat split on the author's opinion here. I also picked up Rails back in the day (I think the first version I installed was 0.8), and I have a bit of a love/hate relationship with it.

As a framework for building comventional HTML templated database backed websites I still think it's near unbeatable, especially with the addition of a few common gems. However it so often gets shoehorned into other places - API backends, rich client apps, and massive systems. Places where the Rails conventions rapidly go from everything falling into place to getting in the way and needing to be worked around, or heavily tuned.

I completely agree that ActiveRecord is the core of why big Rails applications are complex to work with and often exhibit disproportionally poor performance. It doesn't lend itself well to composition, and results in data persistence being intertwined with business logic. That's fine for early prototypes, and in all honesty will get you to market quickly, but it makes extracting the concepts you discover during development into a coherant API much more complex than I'd like.

These days I still use Rails for the aforementioned HTML generating web applications, but it's often acting as an API client to systems built on top of a Grape based backend, with an API built around service objects and a simple data access later.
This was brilliant. Thanks for (re)posting it.

I had never heard of Rota before. I'll have to read more about him. It's a bit sad that he lived for only a couple years after this lecture, dying at the relatively young age of 66. (Wikipedia)
There are always pros/cons to any approach one can as easily argue that without AR your code is less DRY as you need to keep your models in sync with your DB schema manually. (I am not a fan of AR either)
Tell HN: I would like the Scala programming language being separate from Java
Even the Scala Native project, wish didn't need the JVM in order to be built. Scala is great by itself. Good design.
Although I may not agree with your perspective entirely, but I respect it.

I think everyone has different needs, and you have your personal needs which Rails no longer satisfies, so you are moving on.

Rails still solves a lot of problems for a lot of people I believe. I work as a consultant for a few companies and in some cases I see people losing time and money on what would be resolved immediately if they had just made the right call by using Rails.

Good luck on your journey, and remember the rails community will always have its door open for you :). Your projects on github look exciting, I will take a look at them. Very cool stuff!
SUPER MARIO 2016-IN REAL LIFE
Perhaps for once someone is actually trying to tell his story rather than following official documents, which as I said, seem to be prone to a lot of bias and wrong doings.

It doesn't seem to invalidate the account, nor does it seem like the most important comment to give to this story.
I actually have several, since I work in film and tv and got them for free when we switched over to new stuff. :) See here: https://news.ycombinator.com/item?id=11374224 They are heavy, real heavy though.
It's not time that makes Java's TLS stack bad; it's that the TLS stacks are afterthoughts. Java could be competitive with Go if it attracted someone of Langley's caliber to manage a coherent, designed-for-security TLS stack, and then the ecosystem was managed to ensure that everyone used that stack.
Reminds me of Zed Shaw's critique of Rails[0] which explains many of the short comings of Rails. Zed wrote the mongrel server for rails. Assume this article is massively politically incorrect & vulgar as hell, just as a heads up. Really good read though, and does explain some of the interior politics of rails and how it evolved.

[0]http://harmful.cat-v.org/software/ruby/rails/is-a-ghetto
When I was about 15, my dad and I volunteered to help strip cable and waveguide off giant dishes in a decommissioned radio-free zone north of Boulder. The material was donated to a local amateur radio club and was mostly recycled as scrap metal.

I was given some wrenches, a harness, a few carabiners and some rope. I have to say, hanging off those bottom supports with nothing below me was one of the most exciting times of my life!
In Django, the validation & type coercion would typically happen in a Form object (or, if you're using Django REST Framework, a Serializer). That step at least is outside of the ORM and seems much more explicit to me.

Also, in Django models are explicitly defined. There's no ActiveRecord magic of reading the database to define the model. Which is not to say that AR's approach is bad or wrong, but it is pretty significantly different from Django.
I too have stopped using Rails. To other Rails refugees, I highly recommend the up-and-coming Phoenix Framework for the Elixir language: http://www.phoenixframework.org/.

Simple as in simple, fast, productive, beautiful Ruby-like syntax. Favors a functional and immutable workflow over object-oriented and mutable spaghetti code.
The thing that has blown my mind about Elixir and Phoenix is how it gets everything right. It's the clear migration path from Rails.
Rails has plenty of critics. You just aren't looking hard enough.

The most common criticisms are: it's slow and it has too much "magic."

At the end of the day, it comes down to this: every framework has its pros and cons. When you use a framework, you gain certain benefits but sacrifice certain things and have to conform to the framework's opinions. In the case of Rails, the primary benefit is extremely fast prototyping. But that's only possible because the framework hides a lot of complexity from you, which can bite you in the ass if you try to go outside its conventions.
What I'm trying to understand is why all these coding academy students are learning ruby on rails:

To make them have to go back to coding academy school in two years?

So that they maintain legacy codebases and don't touch the new shiny features the experienced engineers are working on until they get their training wheels off?

Because there is actual demand for ruby on rails despite all the hate and sunsetting of rails I see on HN?
I feel like this could be solved with a decent VPN + an occasional webcam.
Sorry, I meant that in a sarcastic way
Telling Drake's side of the story is a fine exercise, but it's not what this article purports to do. Instead, it's loaded with copy intended to bolster it's claims of being heavily reported and of breaking new news. But it doesn't do that.

Here's the kernel of what seems to have happened, synthesizing both the Crane reporting from the Guardian today and the Drake indictment:

1. Drake favored a competing dragnet surveillance system that was pushed aside in favor of Trailblazer.

2. Drake lodged a complaint with the NSA IG that Trailblazer was a waste of money with inadequate technical controls. He is joined in his complaint by William Binney and several other former NSA employees.

3. Concurrently, Drake began leaking to reporters --- presumably, James Risen and Eric Lichtblau, who broke the first major NSA surveillance story for the NYT --- using Hushmail.

4. In handling Drake's formal complaint, the NSA managed to leak Drake's identity to DOJ. The article is fuzzy about exactly which law this violates (it refers to the Whistleblower Protection Act, much of which does not apply to national defense and classified information, and not the ICWPA, which has different procedures and protections). Either way: the White House is apoplectic about the Risen/Lichtblau scoop and uses the leak to raid Drake.

5. In the course of investigating Drake, DOJ discovers (perhaps by first ruling out Binney and the other original complainants) Drake's Hushmail leak. Drake is prosecuted.

The Guardian article would have you believe that Drake was prosecuted directly for blowing the whistle through formal channels. But that is not at all what seems to have happened. Yes, in the process of investigating Drake's complaint, there was a procedural foul (Drake's name shouldn't have ended up at DOJ). But it wasn't Drake's formal complaint that got Drake in real trouble!

Again: I think Drake has the most sympathetic case of all the NSA whistleblowers. His leak was extraordinarily targeted, not particularly political, and clearly in the public interest. I'm not writing to litigate whether Drake was right. I'm saying: the Guardian did a poor job of reporting this story.
Conventions is something I try to avoid at all costs. Conventions are usually things that are hard to find in documentation. Conventions are things that every experienced user says that "oh, this is common knowledge" and conventions are the reason why things seem to work magically.

Obviously if you follow a framework from day 0 you don't even notice it. For newcomers, it's a source of frustration.
Came here to say the same:
http://caniuse.com/#feat=object-fit
Yes, I'm especially surprised that major players give their data to Twitter by including Crashlytics.
Previous discussion:

https://news.ycombinator.com/item?id=6697416 (~3 yrs ago, 311 comments)
That assumes they are nice apps. Not apps that will charge you more when the battery is low.
Thank you my friend, I just fixed it <3
That is not a good argument at all. It's a side-effect of collecting metrics. Uber has no reason to know the battery status of my phone--them knowing it will not help them improve service to me in any way.
I will offer the voice of dissent. Snowden is a slightly improved version of Chelsea Manning and deserves a similar fate as her. Both revealed legitimate issues that they deserve praise for highlighting. However, both also revealed information that has little public interest, isn't illegal activity, and can really only be categorized as releasing privileged material (look to The Intercept and this weeks SIDtoday releases for the most recent examples of this). The intentions of both were noble, but you can't simply say the good outweighed the bad. That isn't how the law currently works or in my opinion should work. You have to take all of the good and bad into account.

As a nation, we also can't set the precedent that any person with classified information has the right to release information they morally object without any legal repercussions. If you are going to ask for whisteblowing protection, you need to be fairly focused on things that are either illegal or at the very least objectively amoral. Neither Snowden or Manning did that. They instead grabbed everything they could get their hands on in the off chance it was something they were looking for. Isn't that the exact problem we have with mass surveillance in the first place?
Having little experience with Rails, it's the tone of that "Crazy, Heretical" article [1] that really strikes me. That tone where you're laboring to describe something that really truly does make sense when you're in the company of a bunch of people that just don't want to hear it.

There's too much purism in those kinds of arguments, arguments that really are more about spectrums. It sounds like Rails is really great for learning the shallowest 40% of a wide variety of programming concerns, and a lot of web solutions for small clients aren't ever going to dip below that 40%. And as soon as you get beyond that 40%, asking questions like "but what if it doesn't make sense to do it that way?" and "what is that weird runtime bug that doesn't happen in my development environment?" and "why can't I refactor without being scared I'll introduce a weird regression bug?" then it's totally fine to be attracted to the idea of static typing, compilation, and libraries/frameworks that are more explicit.

[1] http://jamesgolick.com/2010/3/14/crazy-heretical-and-awesome...
What you said would also apply to, say, the British Empire, which was very Christian for its entire existence.

Most people don't really care about the details of history that much - just whatever narrative they can spin that satisfies today's needs.
Type declarations are similar to Haskell's. Haskell is also whitespace dependent.
Is Django any better?
> Apple doesn't ship GPLv3 code.

I wish Apple would stop being so pig-headed about this. They're about the only major tech company that refuses to touch GPLv3. Google, Microsoft, Facebook; they've all got some contact with GPLv3 code without having their empires crumble. In the meantime, Apple's refusal to ship GPLv3 is doing nothing but making it more inconvenient for its customers to get modern software.

But ever since Steve Jobs got pwned by GPLv2 and thus gcc got an ObjC frontend, Apple has been vowing, "nevar forget".
Here's a relevant book in the works that everyone should keep their eye on. http://beautifulracket.com/

It'll be interesting to compare how "making your own language" is achieved in both guides. Although, the racket situation may be super different, the basic steps seem to be similar.
I was quite happy to walk away from the Ruby on Rails world 4 or 5 years ago. I basically escaped before the onslaught of Rails 3.0 and what came next. I think somewhere around the adoption of coffee script I got pretty concerned.

While at Google I became aware of Go and what that looked like at scale. I would highly recommend trying out Go. I think the simplicity will be a refreshing change but there will also be some familiarity coming from the Ruby/C world, can't quite pinpoint why but just feels that way.

And if you're looking for frameworks, shameless plug, I'm working on this https://github.com/micro/micro.
For anyone who wants to know how all these pieces work together, I've been writing a series that actually dives into the source of Rails:

http://www.monkeyandcrow.com/series/reading_rails/

Sure, Rails is complex, but it takes on that complexity to let us be productive. When you run into that complexity, read the source.
It's not really that complicated. I mean, everything is egregiously complicated if you're not willing to meet someone halfway to interpret what they mean in context, and that's the expectation here. The use of Naturalistic fallacy means here whatever it makes the most sense for it to mean.

Ambiguity is not only a problem, it also has significant advantages.
that sounds like a nice idea! but just imagine such a thing to exist...

they'd need to document these security holes so that the same bug isn't reported several times simultaniously. so, they'll have a database of security holes a documented way to break into them...

this would be more than just a honeypot for every black-hat hacker out there. they'd be swarming them
Then why are we having this discussion?
Ask HN: Do you dream in code?
I recently had a full dream in code (after a long night of js). Freaked me out a little bit but it also made me feel more confident in my abilities. Curious to hear if this is common? :)
Download SoftMaker Office 2016 Serial Key Free
UPDATE: I should have mentioned that was for two people.
Oh, I understand what you're claiming now. But I don't think the effect your describing is very important. As colechristensen points out, the fees in the US are 5-20 times larger while their fraud rate is only about twice. So it looks like other factors (e.g. degree of regulation, monopsony effects, etc.) have a much larger influence on interchange fees than fraud rates. Indeed, the amount lost from fraud is only about 0.1% of transactions in the US, and 0.05% in the EU.

http://www.paymentscardsandmobile.com/wp-content/uploads/201...