skysight-inc/HackerNews huggingface dataset:
> local dialects are basically dead in some areas (for example Milan)

Uela, you have to consider that Milanese dialects basically overlapped modern Italian already - as standardized on the works of Alessandro Manzoni, a writer from Milan. The accents still survive though, and even a few words.

It's incredibly funny to observe language in motion. At one point in the '90s, a few rappers living in the city I come from (Bologna) popularized a bunch of local slang in their songs. Nowadays, youngsters from Milan use that slang as native and strongly believe it originated there.
It probably just means some company that works in pharmaceuticals uses Docker for something, and another company that works in aerospace uses Docker for something, etc.
Kabbage | Lead DevOps Engineer | Atlanta | Full Time

Lead the Kabbage DevOps team to transform our existing infrastructure into a fully automated environment, evangelizing the concepts of “Infrastructure as Code” and growing the DevOps mindset at Kabbage.

Perks: Unlimited PTO, annual bonus, equity in company, full coverage of individual benefits, daily catered lunches, snacks, beer on tap, cold-brewed coffee, dog-friendly offer, onsite fitness classes, adjustable sit/stand desks, and more.

Read more and apply here: https://www.kabbage.com/company/careers/job/679443
The only good point Electron has is 1. All other points are obsolete.

- You can find libraries for "all sorts of functionality" with ease for native languages - Swift, C#, Python (Mac, Win, Linux).

- In the end the ability to use CSS is harming user because now you don't have default OS element styling and every app is using it's own styling for things like buttons - this is very bad.
SEEKING WORK - REMOTE (Southern Ontario close to Greater Toronto Area)

We are a focused team that specialises in replacing legacy systems (end of life databases, misuses of Excel and Access, or manual paperwork) with robust information systems.

Experience in many industries from manufacturing, logistics, and systems at 100+ retail locations.

Technologies include Android, React/React Native, Java, Play Framework, Microsoft Stacks (C#, ASP.net). Prototyping custom designed data collection hardware (RFID, barcodes, etc).

More details available at http://www.opid.ca or email me ian at opid dot ca
That's embarrasing. I just switched over from wordpress to Jekyll because I was worried about getting too much traffic from HN. I think I didn't work out all the kinks. Edit. It should be fixed now.
Congrats on the paper, very cool work. I bet the "Datasaurus dozen" is going to become the go to example for the dangers of relying on summary statistics, it is much more memorable than Anscombe's quartet.
I think it's like everything else, developers see what the top companies are using and think, well, if it works for them it has to be the best (and you can search for "what's the best..." on any developer forum and see what I mean). So in that sense, it's hype driven.

I don't believe this is the best way to decide on a technology.
I've written a few programs in both Lua and Python, and the Lua is generally almost twice as long. Lua tends more forgiving of mistakes which I'd rather be errors, like a missing table key. So though it's great in some ways, it's not my first choice to get something done with.
Just downloaded the app. Can't wait to try it tomorrow morning.

Some feedback, you should use the AppCompat dialog https://developer.android.com/reference/android/support/v7/a... so your dialogs implement the material design instead of the holo design you're currently using.
In the second example the author does the following:

$ ACCEPT="text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8"
$ curl -v -H "$UA" -H "$ACCEPT" $URL |& grep '< HTTP'

The author fails to prefix $ACCEPT with the actual header key. It should be:

$ curl -v -H "$UA" -H "Accept: $ACCEPT" $URL |& grep '< HTTP'
Equity crowdfunding is one of those ideas that sounds super ideal and meritocratic on paper but doesn't really work in practice.

IMO this model will rarely work because of all the non-capital benefits that good investors provide. It's an overly simplistic view of what (good) investors bring to the table. Random people crowdfunding (assuming non-accredited) don't bring the same level of diligence or value.
It isn't at all a black box art. It is true that some exploits can get pretty esoteric, but the vast majority are very simple. Don't use a default password. Don't type your passsword anywhere you shouldn't. Implement a sane access control policy. Use security software in the way it was intended to be used. That is enough to prevent 99% of attacks.
No. The current iteration of Kotlin Native doesn't target Windows due to some peculiarities in it's exception handling mechanism. And Windows is the #1 platform for desktop apps. As much as I wish I could reuse our mobile Kotlin code in our desktop app, that isn't very practical at the moment.
> keep planes in the air

'We really need to land, but the container responsible for landing navigation has crashed and I can't restart it because Docker complains that the endpoint is already registered on the overlay network'

'Just delete /var/lib/docker and re-pull.'
Is it Akamai? Or is it a single site on Akamai? CDN customers can configure their sites in a million ways.

My guess is a single site that was getting DDoS'd added this as an attack signature and forgot about it.
-20% as of this morning, but steadily rising.
Sharkbyte Inc. | Senior React Developer | Montreal | Full-time, Contract, ONSITE, SALARY: 100k-120k CAD

We are looking for a solid React developer to work with us at our large campus in Montreal.

Main responsibilities:

- Design and build rich and complex frontend applications

- Integration with backends and other third party services

- Performance analysis and optimizations in frontend applications

This is a 1-year contract that could be renewed. We would be looking for someone who lives in, or is willing to relocate to, Montreal QC.

If interested, please contact jb [at] sharkbyteassociates.com.
I'm not sure what your point is.

They don't try to tease out whether it was raw computing power or better algorithms, just that it was tens of trillions of times more computed.

Also, minor nitpicking -- they said papers not paper, likely meaning the first several years to decade of it.
Has anyone signed up for the preview? I keep getting "We're sorry, but something went wrong." right after logging in.
I disagree, but that's fine.
Docker was probably a victim of its own success, with so many containers & orchestration systems popping up (CoreOS, Kubernetes, etc.), it became harder for them to capture enterprise market that they had taken for granted. Worse the impression that I got was somehow Docker with its great usability was for amateurs and not for enterprise users (where most of the revenue is expected to come from).

Anyway I think Docker is a great revolutionary product living up to the vision that was initially presented. However it badly needs enterprise adoption to remain viable, all other container systems suck in usability aspects. Hopefully this drives more revenue while keeping the core product still easy to use.
I'd suggest adding line breaks to make sure the comment is a bit more readable. It's kinda tough reading as it's currently formatted.
I think the windows store just did not fit the usage patterns: People were used to download stuff right off the net, or use platforms like Valve's Steam.

On a chromebook-style laptop, expectations might be different.

I personally don't like the walled-garden aspect of app-stores, but I like that there is someone who can effectively respond if malware is reported. Sometimes malware is even proactively removed.

For non-power-users this is definitely an advantage. I hope in a few years I can just tell my parent to only install software from the app store, and they will be fine. Additionally, they don't have to do anything to stay up-to-date.

Even for power users there is a (theoretical) advantage, which is explicit dependency management. Once you know that all your software is distributed through one channel, libraries and versions can effectively be shared. This is what happens in the Free Software version of app stores: All major distros have them, and without them dependency management would be impossible.

So what is the potential gain here? In some version of the future, we might hope that apps don't include hard-copy versions of the libraries they are using, but just tell the app-store which versions they like to use. Security updates can then be pushed by the app-store vendor vs the app vendor.
Mobile Apps specification template for layman
Oh, shield your eyes. The land of IoT is a land of infosec hell.
The two went hand in hand for so long, it's hard not to feel the loss. Smaller transistors were able to be clocked faster - until they couldn't. For a while they were able to use higher transistor counts to get more instructions per clock, but even that strategy is running out of steam. The big news about Ryzen is that it was finally able to catch up to Intel in that regard.
But do schema-less implement foreign constraints at all????

I'm currently implementing a mixed solution where clearly defined properties (and thus ID) have columns and constraints but I also include a schema-less "all you can eat" jsonb field so that experimental properties can be stored.

Upon each release I will migrate validated shema-less properties to static columns or even sub-tables. Similarly if a column is remove on next iteration I might transfer attributes to the jsonb to revert it later if needed. This does include a migration step but this seems only like good practice. Of course scaling... but I'm really not limited by this now.

The client will interact with the model through views or functions so that he don't have to care if columns are real or not. But anyway as soon as PK/FK are needed I will probably straight-out think that jsonb will be insufficient and take 5 minutes to think of a relational way to implement.
Ask HN: What programming feature can't you live without?
Monads? Type Safety? Hygienic Macros?

What's important to you, and why, when it comes to language features?
I've always understood it as an approximate order of magnitude.
We should all be taking offense by this.

This is the drug dealer play book, Hook the kids early, so that when they are adults they go with what they know, instead of being critical thinkers and evaluating the available products to pick the best technical solution for the needs at hand.

this is why small to mid-sized companies are struggling with MS server products, and are locked into this merry-go-round licensing fees. Other products that could alleviate are ignored because of F.U.D. Thus giving us Camps of Pro Apple, Pro Microsoft, anti open source, pro open source.

We should be teaching kids at a young age about all platforms, what they are good for, what they are not. So that we can educate the next generation of workers about computers in general. while not trying to indoctrinate them into a particular platform.

So educators and decision makers please take heed, and realize life is about choice., We should be teaching about choices, and then evaluating the choices once made. Then regardless of the choices we make, we learn from the outcome. If you make a poor choice, you are free to make a different choice the next time around.
Kabbage | Data Platform Engineer | Atlanta | Full Time| Mid-to-Senior Level

Enhance and extend our distributed data platform. We're using Kafka, Spark, Druid, Samza, Flink. This is a particularly exciting phase for the company, as Kabbage offers the only fully automated, online lending platform designed to support continuous customer data monitoring.

Perks: Unlimited PTO, annual bonus, equity in company, full coverage of individual benefits, daily catered lunches, snacks, beer on tap, cold-brewed coffee, dog-friendly offer, onsite fitness classes, adjustable sit/stand desks, and more.

Read more and apply here: https://www.kabbage.com/company/careers/job/649518
Meh. I'm not one to sing the praises of SQL so highly. I understand it's history and its use - but it's also really, really difficult to understand and figure out complex SQL queries.

Personally, I thought REQL was a really interesting take on query languages. As a developer, it allowed you write much cleaner code. You barely need an ORM. REQL kinda sucks for analysts at first, but in the long run, it makes writing complicated queries much, much easier.
I used this site quite a bit when I was first introduced to Lisp.

Reading the first few chapters of ANSI Common Lisp gave me a good understanding of the semantics of the language, and this provided me with a specific explanation of the functionality of each function. Together that was enough to get through my assignments for the class I was taking at the time. It was most helpful for things like the differences between eq, eql, and equal.
disclaimer: I work on openshift.io, and there will be much more coming out as summit goes on so I can't refer to more than in current news:

From https://www.redhat.com/en/about/press-releases/red-hat-unvei...

Team Collaboration
Agile Planning
Developer Workspace Management
Application Coding and Testing
Runtime Stack Analysis
Continuous Integration and Delivery

thus it is more than "just" an online IDE in the traditional sense of an IDE, i.e. Eclipse Che is just one part of it.

All of it running on and targeting OpenShift.

Hope that helps.
I'll toss a comment in from a layman: Isn't it also true that cores are adding more and more specific instruction sets to boost common workloads? Graphics, encryption, etc.

Then you have improved architectures, memory/cache access, inter-core communications... there are more ways to improve a chip.

I agree with your snetiment, for general workloads. I have a 4 year old Haswell and it's working like I imagine the i5s today would perform on a basket of workloads.
I did, but now it's in the status 'waiting for approval.'
Sure. I wasn't trying to minimize it by saying "online IDE". I was trying to say that the home page is pretty ambiguous. I needed help from HN'ers to tell what it even was. "OpenShift" already means something else to me. That list of features you just posted would be good to put on the home page.
Closures and functions being first class objects.

Thank you Swift.
Don't forget that there's a significant chronological gap between being arrested and being imprisoned, and the latter is far from guaranteed.
I've largely abandoned ORMs that generate SQL queries for me. A mapping layer that takes a SQL result and stuffs it into an object (DTO) is useful, but anything beyond that is more trouble than it's worth.

For complex SQL, it's better to write it by hand. You get to tune it and ensure the indexing is correct (either the query usage, or create/modify your indexes), and you get to see exactly what it's doing.

For even simple conditional joins, there's something nice about knowing exactly what's going on, and knowing it's not going to be doing something that results in a nested join loop (eg: the type of slow query you don't notice until you're using it in production and performance suddenly drops).

I'm a big fan of Dapper for this, so a lot of my data layer code looks like:

public IEnumerable<Order> LoadOrders(int customerId)
{
using (var db = GetConnection())
{
return db.Query<Order>("SELECT * FROM orders WHERE customerId = @customerId", new { customerId });
}
}

The one exception I make to ORM-generated code is INSERT/UPDATE queries. For most cases, the ORM doesn't have much it can screw up, and since it's essentially just mapping code ("Name = @Name, Address1 = @Address1, etc") it's more likely I'll make a typo or copy/paste error than anything else.

I've spent too many hours debugging crappy ORM queries, and I find it generally takes twice as long (with quadruple the frustration) to get the ORM to generate the complex SQL you want it to vs just writing the SQL.
The promise of SQL is the ability to do arbitrary complex queries, but the key to making SQL fast is to tailor your indices and queries for the current use. These two are in opposition, so that most of what people do with SQL is do the same simple key-based scans and grouping of linear data sets that NoSQL excels at, except with a big wrapping layer of serializing in and out of normalized tables. Every time I've seen people try to write complex aggregation and filtering tasks in SQL, the resulting queries are either a nightmare to maintain or performance is abysmal.

Another problem is trying to store dynamic schemas in SQL, e.g. data for a CMS with user-defined entities. You either have to expose a version of SQL to the client, which is dangerous and/or a huge hassle (see above), or you have to implement SQL-in-SQL with rows masquerading as columns. Neither is ideal.

For me it was a much different problem though that sold me: SQL has no concept of revision control or conflict resolution, and all update tracking must be done in-band, with manually incrementing versions and timestamps. Doing master-master style synchronization between two SQL databases (e.g. server and client) is a pain. Doing it with e.g. CouchDB was a breeze, because of its git-like revision tracking. Being able to shunt JSON in and out was a huge benefit, as simple arrays and hashes do show up everywhere. Being able to suck in data from production into a developer database using its built-in replication features was great too.

If SQL serves your purposes well today, that's great, but there are plenty of reasons to want to move beyond it. I'd like whatever Post-SQL is to handle nested data types, particularly if it comes with functional-programming-style algebraic closure of the resulting constructs. SQL-in-SQL should just be SQL.

In the meantime, I will just design data-first and acknowledge that how I _pull out_ the data is the main constraint anyway, SQL or not. For arbitrary queries, there's dedicated indexing and searching solutions like ElasticSearch that can actually deliver on doing that efficiently, without lots of careful babysitting.
What is this product about? I clicked "Learn more" and was greeted by a sweet, juicy corporate-speak (https://www.openshift.io/end-to-end.html):

Digital transformation is about evolving into a technology
business in order to compete in the digital economy.
Businesses can’t transform without relying on the developer
to implement the transformation strategy and deliver value.

Mmm... tasty!
10x developer is just a metaphore, not based on some mathematical model. For me it relates to the difference between an average singer in an average band and Prince or Whitney Houston for example.
The live streaming video is at the link.
note that, in C++, pointers to member functions do not close over 'this' [1], so they are not really a reference to a method of an object, i.e. you need to provide the actual object externally to invoke the pmf.

The closure need to be created explicitly with something like std::bind or an actual lambda, and passed around as an std::function (a type erased, generic closure wrapper) or as a template parameter.

/pedantic

[1] GCC does have a very old extension that actually creates the closure.
so much shit.....
There's no place on earth where institutions work to limit president power as in United States.

And no president ever in modern US history faced such harsh opposition.

Unless some cataclysmic event occurs that put in danger the whole existence of USA I don't see anything like that occurring in the next 100+ years.
Follow lifetime changes of a file through the history of a Git repository
I assumed they meant an index on multiple columns (status, category), not a separate table for status_category with an index on that.
Pagar.me | São Paulo - Brazil | Full-time | ONSITE

We're looking for software developers and devops engineers to join our team and help us build the best payment system in the galaxy.

In terms of technology, we use JavaScript, Node.js, Serverless, React, Angular, Go, PHP, Postgres, Mongo, AWS.

Please send your linkedin/git/resumé to: venhapara@pagar.me

Learn more about us at https://pagar.me
Yoyo Wallet Powers the New Caffè Nero App
It has vi in the base system, specifically `vim-tiny`. Vi is mandated by POSIX, so pretty much every distro includes some minimal version of it in the base system. `nvi` is also used sometimes instead.
TripsByTips | Berlin, Germany | Full stack or front end developer ONSITE | https://en.tripsbytips.com/

Our team needs support to rebuild our core application from scratch. We are looking for enthusiastic front end and/or PHP/JS full stack developers eager to design and work with a young, dynamic team.

TripsByTips is a multilingual crowdsourcing platform to produce useful travel content (text, photos, geodata) with 15,000 freelancers in 106 countries and we build software as a geo-service.

The tools we currently use: PHP (Micro-)Frameworks: Symfony, Silex, Slim, PostgreSQL, Elasticsearch, React, ECMAScript 2015/2016, HTML5, CSS3, Sass, Docker, Kubernetes, Gitlab.

Lene Giese looks forward to your questions and application (030-616528400, tripsbytips.jobs@gmail.com)

https://de.tripsbytips.com/jobs/full-stack-softwareentwickle...
ES2015 modules in browsers – the HTML-specific details
Considering the great ties that Concur had with MS - Microsoft!
When you have a hammer everything looks like a nail. I personally hate electron for multiple reasons.

First why would you use web technology to build a desktop app? I could understand if their wasn't a cross platform answer like python and java that are high enough languages that even middle school kids can learn to make desktop apps with. Yet lets default to language and markup language specifically design for a client server relationship.

Secondly from my experience electron runs horribly on linux and windows. I can always tell a desktop app uses electron on my desktop not just by the larger then normal amount of resource it takes to do simple task, but because it will randomly crash. It crashes silently and instantly reboots it self and try to act like nothing happen but it happens so often that I catch it when it does.

Thirdly, I am not about to act like I am some type of security expert, but this is just screaming at me security risk. Electron uses at least 4 engines, how and when do they get updated and security patches installed? Can the programmers stop upgrades of these engines to insure that their app will continue running as is? You can argue all things are security risk, but when you put so many complex engines in one app it is bound to make it difficult to keep up with all the security concerns.

I could keep coming up with more and more reasons why electron is horrible solution to a problem that already has solutions. The appear to webs to keep using technology they are comfortable with is horrible reason to justify this Frankenstein of a code base.
"It works" is a pretty poor reason to continue using something. Horses and buggies work just fine. Automobiles are better.

I think it's important to look at why SQL is still the best tool for the job 43 years later, especially in the current climate of going to production with 6-week old JS frameworks.
Thanks for spotting those problems. I've updated the post. I've debated hiring a proof reader and may do that now as I passed this around my circle of friends before publishing.
That seems incredibly paranoid. Let's say someone parks their car in front of my garage and blocks me in (and blocks the fire lane too), should I just wait it out and not call the police because somebody might die? This happened to a neighbor a few months ago. He called the police, and the only thing that happened was the car getting towed.

How about if you get into a car crash but nobody's dying immediately, don't call the police?

There are lots of situations not serious enough to merit getting someone killed where I'd call the police. I don't think that's crazy. I'm sure it some areas the police are terrible enough that this would be unwise, but those areas are the exception, not the rule.