skysight-inc/HackerNews huggingface dataset:
I'm actually surprised how cheap ESPN is. In the UK, adding the two main sports networks (Sky and BT) adds something like $70/month, maybe more, to your bill. It's definitely not included in "basic" packages but i bet millions of people still subscribe to both. It's pretty much the only reason people have payTV, and something like 60% of households do have payTV as a whole.
As soon my razor, which works with blades, needs to connect to the internet I'll find a different brand.
I am curious, if the fares are subsidized, then how much Uber will earn? I can imagine that surge pricing makes them a lot of money, are they going to drive away surge pricing? What if it is 2am and uber asks for 400$ ( I am not American, so pardon my analogy) to go for a small distance?

Considering the rebellious attitude Uber has, I can imagine their city hall complaint as "this is how we will behave, else we will go out of your city like we did in Austin"
It's provocative - it taunts free society and those who suffered for its sake, for a cause that our society has nearly unanimously condemned. It's overtly disrespectful and intended to cause distress or annoyance. Some would define that as bullying and some wouldn't; either way, I wouldn't care to accommodate those people on my sites.

If someone wants to defend a controversial view, they need to learn how to effectively communicate it, rather than expect others to graciously welcome it. Let the idea's merits be its own defense. If it's only defense is, "well at least it's not technically illegal to say", then maybe it wasn't worth saying in the first place.
What do you mean fire customers in B2B? You can terminate service with business customers anytime you want to?
REST has been extremely successful, having scaled to billions of services, like the one we're using right now.

"RESTful APIs" have mostly been a failure, I fully agree with you on that. The difference is that I think it's a cultural problem; when people like Licklider sensibly thought about a future wherein computers would learn to talk to each other (of which REST is a first step), as static protocols obviously didn't scale, we proved him wrong by sheer brute force. Watching something like Bret Victor's The Future of Programming, it's hard to miss the giant indictment of our whole profession.

That said, since I know the term is hopelessly lost, I don't push for REST either. Our service uses XML/JSON-RPC.
It's an R&D spending cap, to keep the sport more competitive. Much like many pro sports leagues impose a salary cap, so the richest teams can't simply spend their way to victory.
15 CSS Accordions
From the photos of train pushers, the crowding on the Tokyo transit system during commute times is the most spectacularly catastrophic failure mode I could imagine for my life or for society. I've never flirted with a bleaker vision of the future than doing that for 90 minutes a day for the rest of my life. Forget smelly air, that's the equivalent of oxygen starvation.

It's easy enough for me to avoid Asian megacities. People actually want to inflict that on American cities? I have an easier time empathizing with serial killers. This level of sadism defies belief.
Uber is providing infrastructure as a service and it is great. Maybe they can turn into a modern day real world AWS.
You know I have some Ruby code that could use your skills. I really do wish my Ruby would run as fast as my C and you seem to know the magic to making that happen. Can I see some of that code and those papers? I really do want the dynamism of Ruby but combined with the runtime static goodness of C with none of the runtime checking I currently have to deal with. Your confident tone has convinced me those type system folks are a bunch of quacks. The compiler really doesn't need all that information to optimize anything.

Seems like all I need to do is bone up on alias analysis, JITing, and inlining and I'm good to go.
Coal burning has poisoned more food than literally any other industrial activity of humankind. Where do you think the mercury in fish comes from?

https://en.wikipedia.org/wiki/Mercury_in_fish#Origins_of_mer...
There is a premium account for IMDB. Perhaps it is part of the paid service?
AFAIK there are optimization that Java/C# can do at runtime that compiled languages can't do.
This one is soft-MAC I think.
I'll just add one caveat - it's my experience that developers often have little interest in great design code. I write far better mobile design code than any developer I've met (which to be fair isn't many). For me, I contribute best by focusing on that part, leaving developers to focus on their interests which is often new languages, tools, libraries, architecture...
Actually, none of what you said refutes the parent post, rather proves the point. Humans as a group have demonstrated a lack of maturity handling nuclear power.
Now you are changing arguments.
You said: "There is nothing more you can do with x -> 2 + x other than compile it as is."

That is factually false. People called you on it.
Rather than say "yeah, i was wrong, but i meant that in general, one doesn't get a guarantee that it will always turn out fast" or something, you seem to be just dodging it.

So please, can you start with exactly what you would like to talk about?
If it's about inlining, yes, those are heuristics in a lot of compilers, but they also do make guarantees a lot of the time (particularly around tail calling), and in fact, provide the ability to guarantee inlining happens to users.

Fact: If always_inline doesn't always inline, the linux kernel fails to compile and link.

So people rely on it in real software.
Native Instruments Inc. | Mobile Developer (iOS), Full-Stack Developer, DevOps Engineer, UX Designer, Software Test Engineer | Los Angeles, California | ONSITE | Full-time

Native Instruments is a leading manufacturer of software and hardware for computer-based audio production and DJing. Our mission is to develop innovative, fully-integrated solutions for all musical styles and professions. We push technological boundaries and open up new creative horizons for professionals and amateurs alike.

We're looking for people with both the left and right brain fully engaged – exceptional individuals with strong analytical minds and a passion for music and technology.

Full-Stack Developer to create and maintain highly reliable, scalable, and secure online solutions for integration into our products.

DevOps Engineer to set up a greenfield, highly reliable, and scalable cloud infrastructure consumed by our music production and DJing applications.

Mobile Developers (iOS) to work in our Los Angeles office with our team bringing the highest quality music creation and performance experiences to smartphones and tablets.

UX Designer to design and implement innovative, intuitive interfaces for web and mobile applications.

Software Testers to reduce uncertainty about the state of the product so the team can take the right decisions.

Find out more and apply here:

https://www.native-instruments.com/en/career-center/los-ange...

recruiting@native-instruments.com
It's not ride hailing, but...

https://github.com/onebusaway
> I find it funny and think it's pretty telling that there are bold claims made that are only crossed out after the author is corrected

... What else would you expect? The author observed something, drew a mistaken conclusion, wrote it up, and then had the mistake pointed out, and so retracted. I can't imagine the author realised their claims were wrong before it was pointed out, so of course they're only going to cross them out after being corrected. Of course, it's rather unfortunate that an incorrect write-up is being upvoted to the top of HN but that's not the author's problem (other than the choice of the rather clickbaity title...).

For the specifics of this post, there's some subtle differences between how Rust and C++ behave that could easily explain how the author observed differing behaviour and thus jumped to the conclusion, as explored on /r/rust: https://www.reddit.com/r/rust/comments/63ijkw/rust_optimizat...
Manage plugins inside fman – fman Blog
Operation Cloud Hopper
Native Instruments GmbH | Frontend Software Engineer, Backend Software Engineer, C++ Developer, System Administrator, Software Test Engineer, Agile Coach | Berlin, Germany | ONSITE | Full-time

Native Instruments is a leading manufacturer of software and hardware for computer-based audio production and DJing. Our mission is to develop innovative, fully-integrated solutions for all musical styles and professions. We push technological boundaries and open up new creative horizons for professionals and amateurs alike.

We're looking for people with both the left and right brain fully engaged – exceptional individuals with strong analytical minds and a passion for music and technology.

Agile Coaches to actively promote agile thinking in our company, and to support our teams to develop their skills and reach their goals.

Frontend Engineers to build & maintain highly usable, state-of the-art websites and web applications.

Backend Engineers to build & maintain highly reliable and scalable API’s to be consumed by our music production and DJing applications.

C++ Developers to help us evolve our MASCHINE, KOMPLETE, and TRAKTOR software.

Software Testers to reduce uncertainty about the state of the product so the team can take the right decisions.

Linux loving System Administrators to administer and improve our network and server landscape.

Find out more and apply here:

https://www.native-instruments.com/en/career-center/berlin

recruiting@native-instruments.de
Is it really that big of a deal if that happens once in awhile? I'm probably opening a huge can of worms with this comparison, but NHL players play 3-4 games a week all the time. Granted, both sports are tough as hell on the players.
Snapchat's Spectacles [1] offers an amazing example of user experience design as Norman describes it:

“Today that term [user experience] has been horribly misused. It’s been used by people who say, ‘I’m a user experience designer, I design websites,’ or, ‘I design apps,’ and they have no clue what they’re doing, and they think the ‘experience’ is that simple device – the website or the app or who knows what – no, it’s everything – it’s the way you experience the world, it’s the way you experience your life, it’s the way you experience a service, or, yeah, an app, or a computer system, but it’s a system that’s everything. Got it?”

1. https://www.spectacles.com/
I wish we had the kind of money to fund the full development - I mentioned gofundme because a small startup in India will not be able to do that, even though we want to. But I have a feeling that a lot of us will want to us as well.

I'm talking specifically about the usecase of code-execution (especially dashboards).

Here's a small point from me - perhaps you are overcomplicating the usecase for 90% of us. Give a proper ssl/tls+bcrypted password setup and roles: Editor and User.

I dont think you should be worried here in the context of people wanting to run a full on sagemath cloud kind of a thing.

If you can give me a low resource way of letting 100 "Users" on a dashboard form and one "Editor" (who can actually edit the underlying notebook), I'm golden. And I'm willing to bet that so will 90% of your audience.
>There's a small door that opens so the gun can fire. Apparently for stealth reasons. The opening door creates an aerodynamic disturbance and the plane yaws or does something else and the aim is off. So that has to be corrected in the flight software - the plane must countersteer with the tail surfaces when the door is opened. And for some reason it's been very slow to create these rules.

This thing?
https://i.ytimg.com/vi/AJhTDzeMYkI/maxresdefault.jpg

That "door" really struck me as absolutely insane the first time I saw it. I simply cannot understand how a competent engineer could have designed this

When you watch the associated video (https://www.youtube.com/watch?v=JD8mqs93y1s), The thing literally flaps up and down freely when the cannon is firing in static position on the ground. Could they seriously not design it to retract?

This is the first I had heard about the software compensation they added specifically to deal with the drag though. That just makes the entire thing hilarious.
At least some nuclear power plants where designed to withstand a plane crash. E.g. the one in Doel (Belgium) [1] (dutch link).

[1] http://fanc.fgov.be/GED/00000000/2900/2954.pdf
I think the important difference is killing people when running as intended, versus killing people when disasters occur. In a way, a Nulcear power plant is similar to dam; when the dam breaks, it's a serious disaster, but as long as it runs as intended, humans aren't really at risk.
> The original problem swagger tries to solve is: API documentation. So, if you need to document an API, use a format that is created for that purpose. I highly recommend using Asciidoctor for writing documentation. There are some tools for Java that help you with this. However they are somehow technology specific. For instance Spring REST Docs works very well if you are using Spring / Spring Boot.

I have used Asciidoctor + Spring REST Doc to document a complex REST API and my experience was almost complete the opposite for a number of reasons.

1.) Asciidoctor is powerful but exceedingly tedious to edit. It's especially painful to use for documenting an API in advance--wikis like Confluence are far easier to use and also allow commenting.

2.) Spring REST Doc generates snippets of asciidoc text that you must laboriously incorporate into the parent asciidoc. It's particular painful when combined with maven (another source of pain for some of us). Anybody who has asked the question "where do I look in target to find my output?" as well as "now that I found the output how do I make it go somewhere else instead?" knows what I mean.

3.) The unit tests that Spring REST Doc depends on to generate output are hard to maintain for anything beyond trivial cases. I've spent countless hours debugging obscure bugs caused by Spring IoC problems. Also, the DSL format used to define output of examples is hard to understand--just getting URLs to show https schemes and paths takes time.

Finally, I would disagree that Swagger is purely designed to document existing REST interfaces. We're using it to design the interfaces in advance. It's not perfect but works better than other tools I have found let alone informal specification via a wiki. Spring REST Doc is close to useless for design.
Viruses for sure to curb the next epidemic - and put an end to hiv, hpv and the flu.
5 Best Ways to Build Productive and User Friendly Website
Translating technical processes into something people can use effectively... and hopefully enthusiastically.
This will likely be controversial, but IMO both frameworks will "go wrong by default" if your codebase/feature set/team working on it start to get large, and rails is worse. There is no real modularity of features or services encouraged, you by default just have a big bag of models with all sorts of implicit couplings because they're all hooking into each other's public ORM methods and lifecycle hooks and it becomes a nightmare.

By using lighter weight frameworks you're forced to build parts of your own framework in some ways, which can be a bit more work in the short term, but that means it can be optimized for your domain and you can do more to set up explicit boundaries/document how the team should use things. You can also do this in rails/Django, but then you start ignoring the built-in stuff that made them popular in the first place, and there is such a strong idea of "the rails way" that it'll be hard to get buy-in to diverging from that.

OTOH if you're building something that has a pretty moderate scope and aren't worried about it getting too big, both will get the job done fine.

As additional points, rails is also quite a bit slower, and python is honestly a more versatile language than ruby these days (if you want to pull in any ML or scipy code there are obviously a lot more python options).
Are there really commercial BASIC and Oberon compilers targeting ARM microcontrollers? It seems the world is a much richer place then I have ever imagined :)
Sure, and that's a reasonable thing, i'm just saying "the world where nothing aliased and users specify all possible aliasing" didn't turn out to be a fun one either.

Honestly, while it seems a good idea, most languages that allow you to specify complex aliasing relationships tend not to be translatable into usable metadata by anything but very high level compilers in a lot of cases.

Either they have to evaluate the language-level aliasing rules in the compiler (which requires a high enough level IR for them to still be correct on the IR, and means your compiler is language specific), try to translate them into something more generic (which almost always loses info), or fall back to (n^2)/2 space pair aliasing (IE for each n pointer, specify which n pointers it aliases or no aliases with).

They also have to be queryable in essentially constant time for a pointer pair or a memory location and a pointer to have a reasonable speed compiler. This means, for example, if your rule says "they don't alias if every field of every subobject is in blah relationship", that ain't gonna work well unless the answer to that is precomputed and doesn't take up a lot space to represent for the objects.

Most choose the middle ground to make all this happen (or have a high level ir, optimize some at high cost, then choose the middle ground).

So the problem is not usually coming up with cool things you can say at a high level, it's making them usable to the compiler.
I believe, in fact, rust has had precisely this problem with various features, and added a higher level IR to attempt to ameliorate this.

The downside is if you don't find a way to transfer it to the lower levels, you miss optimization at the high level due to not-exposed operations (IE things that are lowered), and then the lower level doesn't have the info the higher level did, so you still miss some optimizations

So you can have the nicest, most complete aliasing specification in the world, and making it help an optimizer may just not work at all.

The late 80's are littered with languages where this was true.
Then the early 90's to mid 90's did the same thing with parallelization.
see, e.g, https://en.wikipedia.org/wiki/High_Performance_Fortran

The paper ken kennedy wrote on it before he passed away is a great read, and led to later compilers, etc, being much better about this sort of thing.
(Rust should pay attention to the "different optimizations", etc parts and hope there is never a second compiler for rust that gains traction :P)
I thought this was dismissed by saying they were left by an unmanned mission.
The Heart of Digital Transformation: Dimension Data
critical mass. just because uber has essentially a monopoly on ride sharing doesn't mean what they do as far as tech goes is not trivial.

uber does many things with their business practices that help them stay the largest provider.
I'm neither working on AI nor a medical expert, but it would be nice to have a dataset with pictures of melanoma and whether they are cancerous or not, to build an app similar to https://skinvision.com/.
Oh, `always_inline` looks like a programmer annotation to me? Am I correct? I don't know. You're the compiler writer who knows about these "sufficiently smart" compilers that should have filled all of that in for me.
Fun Kids Bike Stunts Roof Top
MSA Technosoft, Marketing advertising, search marketing, clickbank
Someone should fairly offer as a counterpart any article showing the myriad of reasons why C++ generates much faster code than Rust in most cases. There are many such articles out there I've seen from time to time.
> are bold claims made

Probably a lack of bold claims of things the author doesn't actually know to be true? i.e. 'lurk moar' in an educational context.

Correcting false assertions isn't as praiseworthy as not making false assertions in the first place. The former is a monkey-patch for a flawed mindframe; the latter is better for all actors in knowledge acquisition and dissemination.
The guy who does backend at Oakmail here.

1. Supporting external APIs greatly helps the cause. Keybase, Facebook PGP.

2. Custom protocols for TOFU key sharing. There has been some effort in ModernPGP regarding that. Not a fan of that.

3. Certificate Transparency implemented for WoT. Something that Gary Belvin from Google proposed during 2nd OpenPGP Summit. Pretty cool stuff.

4. Legacy key servers.

People say that you can't make e-mail secure. Sure as hell you can - the protocol is very flexible and if you cooperate with other companies you can at least create a mini encrypted ecosystem for emails. If we finish the product, we could grab a significant market share away from the competitors and get them to implement new features to finally create proper products.
Won't a lot of them be unable to afford kids?
DPDK Joins Linux Foundation
Okay, i give up. you don't want to actually have a conversation here.

In the meantime, i'll just point out, you can have the nicest type system in the world. It still has to translate into concrete aliasing info about pointers that is usable by both high and lower levels, and is queryable in O(1) time, without taking up a ton of space. Otherwise, it's just sitting there making guarantees no one can use.

"Seems like all I need to do is bone up on alias analysis, JITing, and inlining and I'm good to go."

For most code, yes, actually, that's probably just about right.
> When you have a smart device that's smart enough to be too smart to let you freely benefit from it

What does this mean?
Yes but in that case the scaling technical issues are not your main problem. Your main problem is your business model. Priorities, priorities...
Based on this list, even the summed death toll of these incidences is still massively lower than the single worst incident involving hydroelectricity: https://en.wikipedia.org/wiki/Banqiao_Dam
This is a pity, it's a great editor for collaborating on technical proposals / architecture documentation / etc.

A year ago the Ember Core team was using it for their meeting notes and collaborations [0].

I don't want to see it go. Anyone wants to help out and setup an open source hosted version?

[0] https://news.ycombinator.com/item?id=11384420
An Illustrated History of POSTGRES(QL) [pdf]
SEEKING WORK - Remote

I'm a Fullstack developer coding with 4 years of experience.
Technologies:
* Frontend: Angular, VueJS, Javascript, JQuery
* Backend: PHP, Laravel, Codeigniter, CakePHP, MySQL, Postgresql, Mongodb, Redis, Elasticsearch, BigQuery, Beanstalkd, Supervisord, Gearman, Memcached
* Workflow: Git/Subversion,Composer
Résumé/CV: https://www.dropbox.com/s/792jpli8sx7nmn1/Resume.pdf?dl=0
Linkedin: https://www.linkedin.com/in/ndixita
Email: ndixita@gmail.com
I'm not advocating that designers should code -- far from it. I wish they had better tools for modeling user experiences.

You mention that designers have their own toolchains for prototyping, but these has nothing to do with UI dev tools. I've often wondered why this would have to be so.

Look at other advanced design fields like architecture and industrial design. It would be unthinkable today that professional architects would just draw a facade and not use CAD to actually model the structure. Similarly, it would be very unusual for an industrial designer to model a product using a toolchain that is entirely separate from manufacturing. The assumption today is that CAD and CAM work together, not separately.

Why can't we have the same in software? For my part, I've been trying to work on a solution in the form of apps like React Studio [1]. It's not there yet, but I'm convinced that proper software modeling tools will happen eventually.

[1] https://reactstudio.com