skysight-inc/HackerNews huggingface dataset:
I'm not really sure you understand the situation.

A pharmaceutical company makes a drug which they priced when they acquired it a long time ago, they're the only company which makes a drug for that specific condition.

The drug is priced at $13.50 per pill, which is sold in bottles of 80 pills and is covered by insurance, with a co-pay of $20. Most bottles actually cost only $1, which is a federally mandated amount for a prescription for those on medicaid.

The company (which only has margins of 8%, which is a very low amount) realises that the costs of their only successful drug are going to put them out of business and that they need to raise the price of the drug or stop selling it. This would mean no longer selling the only cure to toxoplasmosis.

They decide that raising the cost by 50x would allow them to continue R&D in to other rare diseases, so they could make other pills.

When they raise the costs to $750 per pill, everyone can still get their pills. The insurance co-pay of $20 per bottle is still exactly the same. The medicaid prescription cost of $1 per bottle is still exactly the same.

Nothing changes for the end user, it costs the exact same, the insurance company picks up the extra tab for the pills and the 2,000 people yearly who need this drug are able to survive.

You should really investigate the situation fully before blindly believing the story the media has sold to you.
V8 is definitely a JIT. It might not have an interpreter in the classical meaning of the word, but it does incrementally compile more as type information becomes available.

It compiles some code, executes it and control returns back to either interpreted code or the framework that decides what to compile next. It's a JIT, because it can't be done ahead of time.

Just doing the final stage of code generation at runtime/startup (like, say, PNaCL does) would not qualify. You could as well generate code for all target architectures ahead of time, but it might be more practical to leave that to the client.

Feel free to disagree with my definition, but I like to draw a distinction between just compiling code at runtime and a JIT, that compiles/optimizes code as it becomes possible.
The best analogy I've seen with regard to code health is that software is not built, not engineered, rather it is grown. Depending on the technology of choice, your garden may adopt to different climates, requires different nutrients, and pleases different audience (or achieves different goals).

From that perspective, JavaScript is a garden where once planted, you can't change anything in your garden, and pretty soon it becomes inflexible to build upon old stuff.

The more tools you have, the better of you can get. E.g. TypeScript, and especially Dart help a lot with tooling (and making gardening fun again). What you end up with is isolated components that encapsulate their own code, HTML template and CSS rules. It may be called web component, angular or one of its many competitor, but eventually that is what brings you sanity.

And speaking of sanity: I've found that "the current hype" is almost always broken, half-baked, and lacks proper engineering practices. Go figure why... Use the tool that you enjoy working with and does the job well, and ignore the rest.
The JIT always runs - there's no interpreter, so if your need to run a method the first thing the VM does is to JIT compile it.

This has some disadvantages - you have to wait for the JIT to run and can't keep running in the interpreter while it compiles, and some advantages - it's simpler.
Twitter's UI is quite good in fact; it does a solid job of supporting the site's core design purpose as a mostly write-only platform for achieving and sustaining Internet celebrity. I don't really understand what all the fuss is about.
> White Supremacists vs. Communists

I'd say nominal communists. Cold war liberation politics was...complicated. British colonial authorities were allied with the west by default, so the "liberation" movements could only get funding, training and arms from communists. In exchange, they would have to show outwards signs of supporting communism, but that was not what they were fighting for.
I don't believe it does any runtime optimization, but it does compile code on-demand. Compiled code returns control to the compiler, but not interpreted code since there is none. IIRC this is done in a similar manner to garbage collection pauses (via interception of bad memory accesses).
That's how Dawkins treats his career as a fundamentalist atheist.
Yes, it is. That is exactly what I have found. It's just insanity. I can honestly say Javascript made me cry today. It's not just you. There is a better way.
What blockchain communities represent the next stage of P2P? Twister is the only thing I can think of that vaguely meets that description, and as far as I know it's not particularly thriving.
> You can create the best alternative in the world, but to actually populate it with users is the task that nobody knows how to solve

Nobody except Instagram, Snapchat, Pinterest, et cetera
Yes you are. The fact that you imagine some causes as evil, doesn't mean anything. And does not diminish the heroism.
Show HN: CloudSlice – Demo, Evaluation and Training Using Cloud
American Growth Has Slowed Down. Get Used to It
A riddle for our time
I'm very tempted by one, the only thing putting me off is the price here in the UK.
To be honest, I don't think startup employees (and by startups I don't mean Dropbox, I mean companies who have to count the cash they spend) are low paid. Obviously a startup can't pay like a company with tons of cash can. In tech and everywhere else. I like working at small companies because you get to do more things, because of the atmosphere, small team, agility, lack of bureaucracy, etc. Where I do think startup employees are getting absolutely screwed, specially in the US, is in the working hours. As an employee, you don't have founder shares. You should just be able to work your 9-5 hours and call it a day. If the founders think there's more work to be done, they can either prioritize better, hire more people, do it themselves, or just accept that not everything they want to do can be done with the resources they have. Period.
James Gosling published a 1981 SIGPLAN paper titled "A Redisplay Algorithm" [1], that used dynamic programming to solve the string to string correction problem [2], which he implemented in Gosling Emacs [3].

>Wikipedia: "Gosling Emacs was especially noteworthy because of the effective redisplay code, which used a dynamic programming technique to solve the classical string-to-string correction problem. The algorithm was quite sophisticated; that section of the source was headed by a skull-and-crossbones in ASCII art [4], warning would-be improver that even if they thought they understood how the display code worked, they probably did not."

>Abstract: "This paper presents an algorithm for updating the image displayed on a conventional video terminal. It assumes that the terminal is capable of doing the usual insert/delete line and insert/delete character operations. It takes as input a description of the image currently on the screen and a description of the new image desired and produces a series of operations to do the desired transformation in a near-optimal manner. The algorithm is interesting because it applies results from the theoretical string-to-string correction problem (a generalization of the problem of finding a longest common subsequence), to a problem that is usually approached with crude ad-hoc techniques."

In essence, it finds the shortest path through a twisty little maze of text and terminal escape code sequences (so different terminals would have different optimal routes to updating the display, depending on what was already on the screen, the length of their escape sequences, if they supported features like character/line insert/delete, cleol, extra padding for slow terminals and commands, etc).

[1] http://dl.acm.org/citation.cfm?id=806463

[2] https://en.wikipedia.org/wiki/String-to-string_correction_pr...

[3] https://en.wikipedia.org/wiki/Gosling_Emacs

[4] http://donhopkins.com/home/archive/emacs/skull-and-crossbone...
Where do pet crates go? I think it might be.
No, when .NET came out computers had gotten fast enough that the JIT pauses around startup were manageable, so they didn't use interpretation as a stopgap like the JVM did (which was created much earlier).
Today is 265th day of the year – Day of the Programmer
This particular day was proposed by Valentin Balt and Michael Cherviakov, employees of Parallel Technologies (a software company). As early as 2002, they tried to gather signatures for a petition to the government of Russia to recognize the day as the official Day of the Programmer. (Wikipedia)
> Richard Dawkins tweet after tweet of him just arguing with stupid trolls, you're supposed to be a respected academic yet here you are wrestling pigs in the mud because for some reason you feel you have to win every argument.

The world is full of "stupid trolls". If you ignore them bizarre things would happen like people starting to believe AGAIN that the world is flat.
Selective enforcement goes through the ceiling, as there's suddenly far more "crime" than anyone knows what to do with.
Yep. Another way to put it is that by ditching Facebook in favor of something open-source and decentralized, you automatically become "that guy": https://xkcd.com/1105/
Yes. But this is only cosmetic. My biggest problem is that when scrolling a timeline, clicking on something, then clicking back, does not take me to the same position in the timeline.
Take a look Su Sandstorm.
Score high grade with the Singapore Assignment Help services of SingaporeAssignmentHelp at an affordable price. Students can email us at info@singaporeassignmenthelp.com and avail more info at http://singaporeassignmenthelp.com/
I hope Volvo's auto mode doesn't cheat-disengage at the last time.
I can see how 3D printing can be used for parts with complex shapes, as a replacement for powder sintering, but there is no way you can use it to cast a single crystal, neither for any part where you need to control texture.
I think we could divide in two types of interfaces: for data entry and for graphics/complex. For data entry, html/css is extremely easy, but for complex specialized interfaces it could be more dificult.
If the control returns from the compiled code, I'd call it a JIT.

Do you know why it's doing incremental compilation? Is there something that can't be done ahead of time? E.g. inlining dynamic ("virtual function") calls and then applying optimization?
Advertisers don't really care about the wasted clicks; they care about the successful ones. If Facebook can give more efficiency (even 10% more) than other forms of advertising, which it tries to do through targeting, then it will attract more advertisers.
The most interesting thing is that y-axis is exponential. iIts humbling that Buffet didn't even crossed 100M mark when he was 40! While wealth accumulation seems to be exponential, it's sure a long winding road.
Giving both sides an actual chance also means that if the person has moved across the country, or is on vacation for a month or two, or so on, that they don’t just get fucked.

Giving them a chance means notifying them in multiple ways, or delaying the process until it can be verified that they have been notified.
The web was conceived for hypertext and doesn't do a bad job of it.

The actual problem is that people took something that was always intended for displaying (illustrated but mainly text) documents that happened to have clickable words that would display other documents, and tried to make it do desktop-style applications too. We've been hammering square pegs into round holes ever since.

And the infuriating thing is we had a great system for doing what HTML+JS+AJAX etc etc does now - it was called NEWS. But those who forget history are doomed to repeat it, first as tragedy and then as farce. Not sure which stage we're on now, maybe both.
Lots of bugs and you need to be an expert on trees, but plenty of green field projects. You get to use rake now and then too.
Best is in my opinion to really practice salary negotiation with a friend. The most important aspects are:

1) Talk about salary at the very end of the interview process (by then the company should know your value).

2) Let the recruiter / manager say a number first.

3) If you get the offer, no matter how you feel, act satisfied, but not too satisfied.

4) Try to negotiate up reasonably.

I talk more about this in my talk at Europython on tech-recruiting and salary negotiation: https://www.youtube.com/watch?v=u6PTaTDHUG4&feature=youtu.be...

Disclaimer: I am a recruiter. If you're looking for a tech job in Zurich, I probably can help you out - you find my contact details in my HN handle.
Maybe it's some kind of dadaist minimalism?
It's decriminalisation rather than legalisation. Basically there are allowed amounts for personal use, if you are caught with more you will face confiscation and perhaps prosecution. Otherwise you are just sent on your way with your drugs for personal use.
A software engineer's Utopia
A workplace providing freedom to design and code, great technology, great learning, no micro-management and a "good" manager (sigh)
You need to adjust for inflation, though.
I feel the same thing to be honest. As a mostly Backend Java guy I just have a hard time to get my head wrapped around the whole Frontend/SPA thing and the multitude of frameworks, styles, tools and so on; just don't help at all. It feels like everyone is reinventing the wheel constantly.

Right now I try to write a simple react SPA and I use more libraries as if I would have done it in a tomcat webapp with static html pages.

Documentation is relatively scarce or non-existent at all and in the end you end up looking at code on github. Hunting on Stackoverflow and blogs written by people and realize that there are 100+ ways to do the same thing.

Looking at code would be fine, but looking at Javascript it's hard not to see how easy it is to write in different styles, which makes understanding the things harder. Also being in the middle of transitioning to ES6 makes it more complicated. Of course ES6 will be a big leap, but ES5 won't go anywhere anytime soon because of backward compatibility. So you will end up with overlaps and weird code.

Sass definitely helps with css. React is a great way to develop nice SPA sites webapps.

I don't know if the whole Frontend part is going in the right direction, but it will need some time to settle. For now it's more fragmented then the Android platform. And it really feels like we are trying to put a lot of stuff on top of protocols, tools and standards which were never meant for this in the first place. We might end up having such big scripts loaded for a page, that it could have been just a thick client instead of a web page.

We threw away Java Apps, we threw away flash, we are throwing away jsp/jsf, PHP, etc... And now we are recreating the same behavior with Javascript/CSS/HTML5. Soon it will be only Javascript and you literally won't write not a single line HTML. (Well React already does that to be honest.)

So yeah, interesting times. And it's hard to jump on this train whilst it's moving so fast.
Zero knowledge encryption's adaption is on the rise, seems like an ideal use-case to me. It will be restrictive or rather complex and will require more work but if you want to work with this kind of data, this should be a requirement imo (in the future).
"So despite all the cheerleading from the Bill Gateses and Mark Zuckerbergs about our recent innovations, Silicon Valley and even many economists have failed to take into account something crucial: The economist’s basic measure of technical progress has been lagging. Overall, growth comes from improved productivity. ... And the data show the sad fact that TFP growth since 1970 has been barely one-third of the rate achieved from 1920 to 1970."

This makes me wonder, in a head-to-head measurement (which would be difficult to do in any sort of correct fashion) would refrigeration beat computers in a head-to-head competition of what raised GDP output more? I'm guessing it would. How about the combine harvester?

Morning dose of humility to our era and work.
"Censorship resistant" also means, in practice, that a large amount of your content is awful. Whereas the average person wants something with the sharp edges removed. Facebook's moderators, inconsistent as they are, are genuinely adding value.
> I think that not only we would have self-driving cars, they'd be working much more reliably than proposed solutions of today, and would utilize some pretty clever analog-driven methods.

More info please?
I would propose the 404'th day of the year?
Portuguese here. From what I know people can have certain doses with them, as long as it is for own consumption. I don't know the correct values thou.
How can nothing change for the end user? If the insurance company is picking up the tab, then the cost of insurance has to rise and/or the insurance benefits have to be cut (i.e. drug is no longer covered or co pay rises).
> it protects your business model by preventing the courts from forcing you to remove that content.

Well, than Section 230 is simply wrong. It's important not to hold Yelp responsible for what a user wrote on his forum, but I fail to see how it can be damaging for a site to delete some unlawful-ruled content (which it didn't create), apart from the immoral case you named.
Because your project is useless when a dependency is removed in the future.
It happened to me one time and now I'm really considering to include the vendor folder in my own repository.

Of course a dependency manager is still very useful to setup a new project.
Uh, taking the average equity granted and multiplying by the average value of equity is flawed on so many levels.

If there's any correlation between equity granted and value, that analysis fails. Also, the average company value needs to be weighted by number of employees. Chances are if you take that average you'll get a higher number.
But then you still have the following hack offenders:

* DOM,

* HTML Layout,

* CSS,

* A small variety of crappy events ( onDomLoaded ),

* a fairly rubbish heavyweight communication layer ( AJAX )

* Keyboard bindings that never work cross app, never cross platform

* Accessibility ??

* No idea of the energy impact of your code

* No ability to do queries on important device metrics ( energy consumption, clipboard, user presence, login / logoff, single sign on )

* History management and back button mess
Homeba Parental Travels in Taiwan
If I understand correctly you are suggesting a block storage solution. But that would then prohibit a scale out, right? (I'm reading on the ObjectiveFS site that it does allow the concurrent access of shares... Hmmm.)

The other solution is object storage, which is the real way forward (IMHO). This route make a app more adherent to the 12-factor principles.
Presumably the reaction to an in-cabin fire will be quicker than to that of a fire in the hold.

A couple of decades ago I could see that, but nowadays? Surely installing an array of heat and smoke sensors wouldn't be that expensive?
Mostly to avoid compiling much code that doesn't actually get executed. For the most part you can do everything ahead of time via static analysis (Xamarin's iOS toolchain does this). The only exception is access of code via reflection, which is harder to statically analyze and will also invoke the JIT.
Most of these are very obvious (like move your expensive code out of loops when possible). Some of them are just wrong. And the rest are very basic stuff and even nonsense (like avoid empty static blocks, who would write an empty static block?).
That on top of the fact that the examples use the slower StringBuffer instead of StringBuilder.
Child Maintenance Calculator
COBOL is actually very good money nowadays. There are more legacy systems than programmers left. Learn COBOL and #StayAflotForAWhile
Any idea what the other implementation spent all that time on?
Permutive (YC S14) is hiring an iOS engineer in London
Thanks for your feedback.
I'm trying my best to make it faster. Because It's based on analytics warehouse (BigQuery) it's not trivial...
This is a bad excuse.

Today you can do a Facebook that lives in your own server. Your server living in your house and being a simple box that you can buy like a TV or car and is super easy to configure.

I already have something like this, but it is complex to configure as it is not mass manufactured but custom made for me and a small environment of people.

Everything else, an excuse for not working on finding solutions for the problems that you have to face, like with any engineering problem.

Of course you can't replicate the work of more than 500 programmers(facebook) with just one person, but you can go far reusing open source components and coordinating the work of other people.

Instead of trying to replicate facebook(a clone), focus on making something useful for the people getting advantage of distributed computers. Facebook did not try to replicate myspace.

For example, focus on networks that PAY real money for having a social media they can control(companies).
I agree with you here. The front-end (JS, CSS, HTML) are there to stay and can be organized into clean and maintainable modules. Its not technically difficult but it is humanly hard: you need to put in place best practices, peer training and have lots of discipline. Lots of people are turning to React - probably because it gives you structure.

Often a developer is thrown into a stack that was built crooked and gets discouraged. Instead, its your job to get in there and clean it up. It may take months but you'll you yourself and your team a big service!
S/he means that the core problem in creating a "Facebook killer" is not creating a social network, but figuring out how to get users through it. Instagram, Snapchat, Pinterest etc did not use any new protocols or tech, but they were able to attract users and grow through their distribution methods (on mobile) and features (not their underlying tech). Using a new P2P protocol will not attract enough users to beat Facebook.
Lol what is KVM thanks for the no link on the readme.

Dear Internet, can we stop using acronyms without defining them first? Thanks.
Which specific ones, for example? "Every one" could cover a lot of ground and doesn't have much information content. It's doubtful you have experience in every one, and it would be useful to know which specific ones have been tried and seem better.
You don't need this technology to do it but it sure makes things easier and faster to do. Allowing you to automate the process and apply it on a huge scale, say for example every letter handled by the US PS.

Up until now these would have been specific and targeted attacks where the benefit was worth the effort of the task, with little effort required they will have no reason not to.
I just hate it when variables won't, and constants aren't.
>I once liked a dance company on Facebook because I know the person who made their website. Now I see adverts for dance productions. That's not advertising gold; that's a waste of advertising money.

I think it may be more subtle than that.

- not all clicks are created equal: clicks advertised to people like you might be cheap, so why not pad out the "gold" budget with a few chances elsewhere?

- the advertiser might be targeting incompetently and hoping for the best (possibly even succeeding!)

- you might coincide with 90% of "gold" clicks --> still worth it

- your demographic might be an experiment

- etc. etc. etc.

Marketing seems - to me - to have an awful lot of "let's make assumptions and test them" about it. With anything like that, you're going to reach people who aren't interested.
Not fair, if just make some simple UI stuff, html and css can be the same easy as WinForms.
Dynamic programming is, embarrassingly, one of those topics I've never quite grokked. Any recommendations for a "OH... I get it now" explanation?