skysight-inc/HackerNews huggingface dataset:
If you want to consider every facet of backend instead of the few main ones that show up when you want to solve a problem X in language Y then why claim frontend is just Js?

By your reasoning for backend, frontend sucks because I could probably find Open GL wrappers for every language used on the backend and make a front end.

Backend really is relatively simple because usually language X has a few really good libraries/frameworks you can pick up. Js is Node.Js. Python is Django or Flask depending on what you want to do, Elixir is usually Phoenix, etc.
read the last quoted sentence
Thanks! Flynn is designed to be cloud-independent so you're not locked in to any cloud, or even cloud in general. You can also run Flynn on your own servers.

Flynn also allows portability between clouds. Since we don't use any cloud-specific features (like, say RDS) you can backup a Flynn cluster (including database appliances) from one cloud and deploy onto a new cluster on an entirely different cloud.
I imagine that it is in part because it's easier to fret over the polling numbers than it is to convince someone supporting the opponent that they're wrong.
Unbelievable that auto update is the default. Got bit by that.
Let's see if I got that right: Specification says I must load the AMP script from cdn.ampproject.org?

If yes, then there is no effing way that I will ever use this. I will NOT use something that forces me to load scripts from a host that I have no control over. Does nobody see what a HUGE security risk that is???
The problem is not the tooling, the browsers or JS itself, the problem is that JS developers are trying to put themselves EVERYWHERE THEY CAN in attempt to pursue the now infamous "full-stack engineer" motto.
Out of curiosity (and because I'd love to read more), which of your old blog posts would you MOST expect to randomly resurface at the top of HN?
It depends on the project. Is it a web application for keeping track of daily tasks? You probably don't need that much rigor. Are you building something that if it fails will harm/kill/cost people a lot of money? More rigor is needed.
What other security hole is there for web devs to handle

Ironically, as we introduce more expressive power in the browser (an untrusted execution environment) to support SPAs, we are actually introducing more security issues:

http://intercoolerjs.org/2016/02/17/api-churn-vs-security.ht...

These are the crazy years.
I am already enjoying benefits of grouplization. Real-time traffic is monitored via millions of smart phone GPS and Inertial sensors. The data (may or may not be satisfactorily) anonymized, and analyzed and sent back to my smartphone to make route decisions when commuting.

But its a slippery slope that consumers slide down over and over. I recall days gone by where SUN Microsystems engineers engaged in heated debate about caller ID and whether that was too much an invasion of privacy. Then, they argued that online sales would never take off because of the weakness of Internet security.

Yahoo's patent application seems to me to be a natural outcome, once our smartphones are outfitted with so much sensing capability. Be outraged, but don't be surprised.
This week in tech
I think Unity isn't too bad about screen real estate and mostly staying out of the way, and I like the Cinnamon throw back a great deal. But what I like most of all is chucking the entire desktop metaphor into the bin and using a tiling window manager with a simple status bar and a launcher like dmenu. It's the biggest upgrade I've ever made to my computer interface, and ever since I made the move I find real desktop environments to be universally gimmicky.
Indonesian gay couple arrested over Facebook photo
Orion would have exhaust velocity ~1000-10000km/s. Compare that to NSWR's 66km/s. NSWR seems fast compared to today's chemical rockets but it's nothing compared to Orion.
I'm blown away by how small the implementation is.
That is completely unacceptable behavior. If you were in my company I would petition to have you fired. I hold a strict no asshole rule, life is too short to work with people who would do something like that.
The problem with that it only tells us how good they were on election day. It'd be great to somehow evaluate their earlier predictions, which is probably only possible by looking at an aggregate of election.

(or maybe, since there are predictions and results for every state and every senate race, it's actually possible to use those for an evaluation. Note that it's not as easy as scoring a "won by trump" in favor of a forecaster who was giving trump a 60% chance. You need a measure that expects your 60% predictions to be wrong 40% of the time, like the Brier score)
...ZeroHedge? Really?
Australia's cyber chiefs want to stamp out the word 'hack'
> unnecessary for the vast majority of web applications

There's a sliding scale of what counts as "necessary" to different developers. For example, the first entry in the intercooler.js examples is a "Click To Edit UI" that doesn't escape HTML in user input. For many websites, that probably doesn't matter all that much, but for developers that care about script injection, they might go for a different solution that makes that sort of problem harder to introduce. That exposes the underlying complexity though, since using string concatenation to generate HTML is no longer a safe option.
I think there's a divide here -- "websites" you and I and the rest of HN visit, and "web applications" which are non-trivial interfaces to complex data. If you're using Webpack, React, Redux, Typescript and NPM to render basically static content you're doing it wrong.
And he came out of an aquarium (i.e. 90° walls + 100% humidity)
Yeah, in a way a lot of those discussions were a last gasp of folks trying to do things correctly, before everyone learned to just relax and enjoy going with the flow.

It makes me sad to read them now, a decade or more later, and think of what might have been.
Laughing at someone's code is like laughing at someone's painting or their novel or really any other creative endeavor. It's not ok period.
No problem..
> what other security vulnerabilities for Web devs to handle besides csrf

Not defending the article but the more intertwined the client and server code becomes, as well as server side development in nodejs etc , the more security vulns javascript developers will be exposed to.

In addition nodejs has become arguably THE introductory web development language and as such offloads many complex but necessary tasks to its third party libraries in order for beginners to develop efficiently. This means security features ranging from CSRF to ORMS to CORS etc are taken out of the domain of developers and into that of typically un vetted third party libraries, becoming a vulnerability in and of itself.
Networking and Recommendations: Your Weapon for High-Class Recruitment
Carbon Nanotubes Finally Outperform Silicon in Transistors
Those bloody Canadians though...
thanks, this is actually what I came for, to see how can you implement real embedded tasks in Lisp. GPIO, ADC, timers, etc
> strong/weak as an alternative to expressive

Expressiveness is always relative to what a system is meant to express. The purpose of a type system isn't to write your actual programs in it. You use a type system to make sure that programs written in another language (a term language) make sense. So a type system is expressive to the extent it accurately captures the distinction between programs that make sense and programs that don't. (Of course, Goedel tells us that no decidable type system can perfectly capture this distinction.)

As for strong/weak, I don't think the concept is very useful without a clear technical definition in the first place.
The Weekly Roundup – Web Design Tutorials by Solodev
Questions I wish Yarn had answered on day one
Or Etsy.

I think your comment about C is right, however in many cases mercifully the C code isn't facing the internet :) When it does, it can go very wrong, e.g. OpenSSL.

The extra cognitive load doesn't guarantee failure, it just makes it easier to slip up. Even with Python or Rust, you can put insecure code in there (e.g. with Python's subprocess.call(..., shell=True)). Realistically, strict modes and linters are always a good idea and can catch most of these pitfalls.
I Turned a Gifting Shopping App into a Game Here's the Result
...and this is the opponent's technology:

https://news.ycombinator.com/item?id=8925019
Have you ever looked into how many businesses do nothing but set up WordPress sites for customers with light customization? Quite a lot of companies want such services.
Great. Now we only need 330 more of those.
Of course there are the heat islands that would skew weather patterns and actually cause more warming...
No, spam is more akin to door-to-door soliciting.
the article's questioning the validity of all these estimates (usefulness), and you're mad the wrong guy got all the credit?
There are simpler reasons. Being able to direct the polling is useful (spend resources on a given issue or not). Being able to spend more polling resources on close races. Having guaranteed access to the internals of the poll. Etc.
That's because I'm using a library, mockjax, to mock out AJAX requests for the examples, to keep them as simple as possible. Any sane server side web framework is going to escape HTML for you.
People are worried about how they are perceived by other developers. It's the same reason a lot of people loudly pooh-pooh GameMaker (citing Godot, UR4, Unity, etc. as superior) even though it's a super powerful tool that, in the right hands, can be used to rapidly prototype very complicated and versatile games.
MongoDB -- New York, NY (ONSITE) | Triage Engineer, Server | Full-Time | Base + Pre-IPO stock Options

We're looking for a versatile, fast learner for a Triage Engineer position on our Core Server team. This is a very challenging position, with huge growth potential. This team builds and maintains tools, infrastructure and processes to improve the development process and release quality of MongoDB. Part of their mandate is to troubleshoot user-reported problems and report bugs back to the the Server development team, so those bugs get fixed in future releases.

The ideal background for this role would be Linux Systems Administration, with experience supporting back-end services, and scripting/development skills for tooling.

Any interest? Please reach out to me at Matt.Leva@MongoDB.com or apply here http://grnh.se/gyfx1q1
Definitely. I have a similar policy about deploying late in the day on a Friday. Rushing to get something deployed before an arbitrary deadline is generally a bad idea. By all means, push hard to finish the feature and qa it thoroughly, etc., by whatever cutoff, but wait to hit that launch button until the next morning. Saves so much stress.
This is a pain point I hear about a lot, usually with the suggestion that we should do LTS or a rolling release. LTS is very expensive — and I think prohibitively so for our volunteer community. It's also at odds with our desire to get new upstream software to users quickly. You didn't mention rolling release, but I can get into that if someone wants.

In any case, we definitely hear this and our approach is make upgrades as painless as possible. We've put a lot of work into this over the last few releases, and the feedback right now is very positive; I'm seeing a lot of "wow, that only took 10-15 minutes" on twitter from beta upgraders.

From the command line, it's one command to prep the update another to reboot into the offline update itself, and then you boot into the upgraded system. When F25 final is out, users of earlier releases can even launch this from the Software GUI, just like a regular security update.

As for UI changes... I think GNOME 3 has really settled down here, and most changes you see will be minor tweaks and usability improvements. As of Fedora 25, there's no longer version checking for extensions — we expect them to just keep working for the most part. That's both a result of increased stability in the shell interface itself, and a sort of stability feature in itself.
Yes, it's just a matter of swapping a few pointers and fixing inconsistencies with blocking clients, however this was conceptually possible thanks to the "lazyfree" work that is able to reclaim the old DB incrementally, and is a much larger implementation.
Not sure which sentence you're referring to. And I'm not saying there's no way to tell which probability assignments are better. I'm just saying that the mere fact that an event assigned a lower probability happens (e.g., if Romney would have beaten Obama in Florida) does not mean the assignments were wrong.

This is consistent with Silver's own explanations of what he's doing, and (I'm pretty sure ) he is careful to say he doesn't make "predictions". (Actually, not sure, it may be merely that he often clarifies that a different result than predicted does not make the probability assignment that prompted the prediction "wrong". The prediction and the probability analysis it's based on are different things.) I'm not saying that the Brier Score can't differentiate between better and worse probability assignments, but I am saying it's confusing the issue if it calls probability assignments "right" or "wrong". They may be "better" or "worse" than each other, but not "right" or "wrong". This may be using language in more technical manner, but it seems to me (and to Silver) to be an important distinction.
A lot of open source JavaScript libraries are MIT licensed, including intercoolerjs, and the concept of "under no obligation" is directly encoded in that license:

"THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."

[0] - https://opensource.org/licenses/MIT
How this ‘startup studio’ axed 22 ideas and spun out three companies in one year
Originally, a TeX user would've been called a TeXnician, which, according to Don Knuth, would be pronounced the same as "technician."
I've always felt this attitude towards giving trust to the new hire is a good thing. It remembers me to something I read not so long ago where a Perl core contributor makes the same thing with collaborators.

What I don't find ok is to blame a person for an error going to production. Specially when the error is caused by the lack of supervision to the new hire code (code reviews) and probably QA.
> jump around the source code

A named function should be easier to track due to it being named, and properly defined in one place.

I believe debugging can be harder when you see some random anonymous function and have no idea where it is defined (because, I think, lambdas don't hold their definition line-nos?)

Since we're talking about multi-line functions, the added verbosity wouldn't be a lot. Additionally, you would be forced not to nest functions too much.

> why static analysis can't handle closures

Would it require tracking run-time state/modifications to the closure?

> I want to use expressive constructs as a programmer, not be arbitrarily limited by what some static analyzer can handle.

You could argue the same for any language with types - why should I be limited by the constraints of the type system?

Because it's easier to verify the code, and it doesn't actually limit what's possible to develop, only how it must be developed (in a more explicit style).

I see it as putting an extra burden on the developer, which makes it harder for sure, much as writing tests puts an extra burden on the developer.

> why they can only be one expression

http://www.artima.com/weblogs/viewpost.jsp?thread=147358

Seems like it is mainly a technical decision.

> I don't want to limit my expressiveness because of some technical issue in a language

I feel this is a problem with js (versus, say, Java) - faster to write, harder to analyse. What's so important about expressiveness that you wouldn't want the code easier to maintain?

> Many languages implement closures efficiently

I can't really complain about this wrt Python when I'm not sure what it would add. Even if lambdas could be multi-line, I would not want to use them for sake of their parameter-binding semantics - in fact, I consider it a python gotcha. I
The bit that made the decision for me is managing self healing, highly available postgres in the same infrastructure and tooling as the rest of my deployment.

I have yet to see any other PAAS come close to offering HA postgres built in.

The second bit was dead simple service discovery.
EpycsMessangerAdvanced
New release of first ever in the World Skype Network Compatible client will be at 30 dec 2016.

30 dec 2016 release will contain three versions of EpycsMessengerAdvanced:

10$ BASIC version at pre-order - with basic send/recv chat functions.
after release date - 25$

100$ PRIVILEGED version at pre-order - version with optionable skype functions
like not anounce youself to skype network, OTR, show ip of connected users.
after release - 250$

And 1000$ VIP VERSION pre-order - with functions like in priveledged version.
but with newest added features. Like users search, contact list add/remove, and other small unannounced features.
Also, you will be granted and get personal account to this sites:
- access to skype users monitoring center
- access to skype protocol knowledge center
after release - 2500$

All prices for per year support.

This is first round of release. If it will be financial success, in next year release i will think about adding sound and video support.

Payment methods listed at donate page. Bring mail to skypeopensource@gmail.com after payment for getting your client-id.

http://skype-open-source2.blogspot.ru/2016/10/epycsmessangeradvanced.html
Thank you for writing this - very eye-opening. One sentence doesn't seem right to me though:

> Hack provides an option that no other popular member of the MPDPL family has: the ability to introduce a type system after initial development, and only in the parts of the system where the value exceeds the cost.

Python 3 allows you to do that, too: https://docs.python.org/3/library/typing.html
Saddam Hussein's NYC torture chamber across from Mayor Bloomberg’s mansion
I'm a little skeptical about following this link. Why can't you just give a direct link? Who knows where that link will lead to? I certainly don't and I'm not about to try it and become a victim of drive by downloads, etc.
Choosing GraphQL as your startup's main public API
it's a binary event, so differences in degree are going to be difficult to measure (especially in outcome). poker has an interesting add: don't measure your play by outcome; get the process right and results will follow. if you focus on outcome, you're likely to believe you played poorly when in reality you were just unlucky (something unlikely happened).
Once AMP stabilizes, I'm hoping Google will encourage the use SRI to ensure that the content is what a site expects: https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
I'm very glad someone made this point.
For a browser?

1/3 or more of desktop Windows users are on 32-bit Windows, last I checked. So you definitely care at least about ix86 of some form.
"Also note that Wang & Ferguson got a better Brier score than Silver despite getting Florida (barely) wrong while Silver got Florida right. The Atlantic Wire gave Wang & Ferguson only a “Silver Star” for this reason, but our more detailed analysis shows that Wang & Ferguson probably should have gotten a “Gold Star.”"

I think being concerned about this authors usage of the words "right and wrong" misses the point. The media will say "you were wrong" if you were on the wrong side of a 51/49% prediction, even if you shouldn't be penalized for it. Wang & Ferguson got dinged by The Atlantic Wire for being wrong, when they shouldnt have. The last quote in my post, supports your point. The person who is least wrong is the person with the lowest aggregate Brier score. The author was using right and wrong, because the articles they were referencing used those terms. The quote was written with the colloquial language of what it addressed.
Do you have proof of this?
> We're copying useful features while avoiding copying the bad parts. This robot's not going to get cancer or die of old age, and we can replace its limbs with a screwdriver.

Well, it won't get cancer, but the memory will suffer bitflips over time and tin whiskers will eventually cause shorts. It will also stop working at some point, like all machinery.

Not really disputing that this is impressive. But mechanical systems just have different longetivity problems than biological ones.
You can't. A forecast is just that - a prediction.
There's complexity of tooling, and complexity of code. I'll take simple code over simple tools any day. The package.json in my SPA is bloated but the majority of the code is pretty simple and the bits that aren't are well-encapsulated.

Back when I was using just jQuery and maybe Backbone or KO the tooling was simple but an incredible amount of rigor was required to keep the code maintainable. A big part of my job right now is providing a dev environment where people don't get fatigued -- most of the tech decisions I make are geared towards ease-of-use by backend devs. Sure, the toolchain is relatively complex, but it's a fundamental part of why I'm able to do that.
The Dacians – Europe – elearning
The mobile market is bigger and still growing. Desktop is shrinking. It's a simple financial decision.
Because it's usually a raw socket, not an HTTP interface, so that's kind of tricky. But it could work.
The law of encryption workarounds
No, all of the medications seem to be lumped together.
It is very simple. All one has to do is imagine the election being repeated an infinity number of times under a stationary-non-changing distribution.
People haven't actually agreed on a single definition for what 'probability' means, although we have various definitions that often lead to the same numbers in practical cases [1].

[1] https://en.wikipedia.org/wiki/Probability_interpretations#Ph...
Yeah, only door-to-door soliciting to a point where you have to jostle a crowd of people whenever you try to exit your property through the main door, and they try everything in their power not to budge.
I've never worked on PHP code in a truly professional context, but I've had one-off (very) small jobs where I've had to perform maintenance on some PHP. I have no doubt that the language and tooling has improved over the years, but I have no desire to ever work on any of it ever again. This is my honest opinion, and I'm not writing it to signal anything. There are dozens of viable production languages and life is short, so why work with one that you find very painful? If PHP works for you, that's fine, but people who don't like PHP are going to be vocal about it because they don't want to find themselves in a situation where they have to write it. You might not end up being forced to write PHP for pay these days, but it's not unrealistic to imagine that you might end up writing (for example) Java because you need a job even if you really don't like it. So you end up with language advocacy and trash talking and there's nothing wrong with any of that, it's just a way to let off steam and preserve your sanity.