skysight-inc/HackerNews huggingface dataset:
What do you mean? I'm interested. Do you hace a link to a longer essay on the topic?
> Support for institutional installations: A central build daemon + farm is a pretty lame say to synchronize things. Should make it so anybody can build stuff, and anybody can share binaries with those that trust them, and shared NSF store or equivalent for de-dup.

At the research site where I work as a software person, we use a central guix-daemon managing a shared NFS store. Anyone can build stuff and manage their own software profiles from cluster nodes. Works very well for us and gets us a big step closer to reproducible science.

Sharing build artifacts also works with Guix. You can either export from and import items to the store or use "guix publish" to share items via HTTP.
Record for fastest ever data rate smashed as 1.125Tb/s reached
Well, my wife is actually my favorite Existentialist ;)
But surely as more and more data is gathered over the next decade , this sort of thing could become feasible ?

For eg: I know for a fact that FB is betting very heavily on travel advertising. FB wants to be the go to place for travel companies to advertise their products , so FB has an incentive to make people travel more.

They could do this prominently highlighting when people travel to a certain tourist spot etc...
As one middle manager pointed out to us, at Apple the top managers are engineers. “We make everything into a business case and use figures to prove what’s good, whereas Apple is engineer-driven.” Top managers acknowledged to us that “there was no real software competence in the top management team”.

That stood out for me. Whenever I've worked with managers who didn't understand the field, interactions have always gone something like this:

Manager: Can we deliver X?

Team: Sure, it will take 3 months.

Manager: Can we deliver X in 2 months?

Team: No, I told you 3 months.

Manager: I need it done in 2...

And how it proceeded depended a lot on how bone-headed the manager was. Sometimes they would effectively let someone competent on the team do the management. Sometimes they would just try to bully until they got the answer they were looking for.
There was one good point, which was also my conclusion:

"Given all that, I wonder if it makes sense to prefer plain old functions most of the time. Is that right, or am I overlooking something?"

The response was yes. Avoid impl methods which take a mutable self.
React and Webpack are both awesome, they both work across server and client, they complement each other rather well. Obviously they are mentioned together a lot.

You can use React without Webpack just fine, as the article shows you can use React without any bundler at all. But it is just so much better with Webpack. When you really start making components and put them in separate files, the raw approach in the article will not scale very well.
First: I entirely agree with you regarding DRM. Second: the "baseless framework" of property rights is how it has worked for centuries. Hardly baseless. The new world is the exception and I don't see how it has materially changed the rights of a creator to their own works.

I will say that our current system is extremely broken with regard to the public domain, primarily because of things like DRM and intellectual property, both of which I believe are harmful to society as a whole. I also believe copyright had been extended for way too long. These are things we should push hard to change because I agree, they break the implicit agreement that justifies copyright.

But in the world you are imagining, every new work of any kind would have to be registered with someone to make sure the sources are made public when the copyright expires. Then of course, you would have the massive enforcement effort to ensure the sources actually get released. Little Jimmy starts working a little game on his parents' computer? Better register that with the copyright office so the sources don't get lost in ten years when the copyright expires. It's ridiculous. That's not the way it works and its not the way it should work.
You can still have management by perkele but make sure management understand what engineers actually do.
TPP is obscured by a wall of confusion and disinformation. As a tax payer of the United States (or any other country involved), what do you think the takeaway is? As in, how should I, a concerned citizen, approach this topic at the bar or the dinner table?
When trying to think about how you might prove this (I'm taking a break from proofreading an acquaintance's criminology paper this very moment), it occurred to me that by virtue of keeping people off the streets, the Internet will decrease arrest and other criminal statistics simply by decreasing exposure to predatory police who have arrest statistics to maintain.

Taking that further, it could mean the focus is even more intense on those who do go out, and when you go out. I suppose you could try to measure this by finding historical statistics on where people spend their time, inside our homes our outside. After dealing with confounding factors like decreased employment.
Manfred Mohr, the groovy German who taught computers to make art
Nokia had long term plan which looked promising: They bought first Trolltech for QT and after that started doing Meego* (albeit too slowly) but the idea was to have one development platform for all their new and old phone platforms and QT fit the bill really nicely. But in the end the QT plan was really half-assed because getting it into Symbian took too long time and Meego was even slower project.

The first Meego phone N9 and it's unpublished sibling N950 (with the best qwerty hardware ever) were better phones than Android phones at that time, but when they released the N9 it was already known that Nokia will switch to Windows Phone and there was no point in buying N9 or developing apps for it.

They even had the QT + QT Quick setup working and showing lots of promise for writing javascript apps for different platforms. Sigh.

So if they've had the guts to execute the QT plan and Meego as a first priority projects + skipping Elop, the situation could be a lot different. Meego still feels more Linuxy than Android.

* Of course creating first Maemo on top of GTK and after that switching to QT sounded weird and with Meego there was other parties like Samsung and Intel meddling around so they lost lot of steam in that transition too.
In this case one of the programmers is a researcher. That has applied for grants to work on Sage. Grants that also funded other programmers (grad students and the like).

http://wstein.org/grants/
The Sexual Misery of the Arab World
Symbian wasn't even home grown.
Based on the ads I have seen Google hasn't yet moved from "this guy is looking for an apartment so lets show him ads for the same apartment deal site for months" to "this guy has looked for a apartments for a short time and now doesn't, lets show him ads for some curtains" so it seems even the best predictors aren't very good yet.
>Nokia needed a better operating system for its phones to match Apple’s iOS

I strongly disagree. Symbian just needed a few optimisation, which it got. It got them too late, but it did. Maemo/MeeGo was probably more capable than iOS is today. And what exactly are those "quality problems of N95" they speak of?

Nokia was indeed wounded by incompetent management, but Microsoft was the one who stepped in and finished the job.
The real solution is 'import' but we probably won't see that in ++17
Very interesting read: http://muropaketti.com/artikkelit/the-story-of-nokia-meego
The "unreadable" or "annoying" example from the article is only unreadable and annoying because the programmer was new to the project when he read the two offending lines of code.

I believe Stroustrup is correct that we're all beginners at some point, but we quickly move up. It makes more sense to optimize for "proficient, but not expert" than to optimize for "beginner," because more people are at the proficient level, and they stay there longer.

I agree that code shouldn't be unnecessarily complex. But I would quit any project that constantly brought up "but what if a programmer were brand new when they looked at this code?" in reviews. Then again, if other programmers have the same reaction, perhaps the project really would be full of nothing but beginners.
Based on the people I have talked with, who are non-technical, and need an adblocker, it was youtubes commercials before the video that made them install the adblocker, not any idea about tracking.
> Meego still feels more Linuxy than Android.

...is that supposed to be a good thing?

Edit: snark aside, I'm not sure how this would be a factor in what makes a mobile platform successful. It feels like the sort of comment that would be made right after saying "year of desktop linux!"
They'll get it, in a couple of years, when the outcomes of their business ventures are nowhere near where they expected them to be :)
Have you got some links to studies? I know someone who is starting a web shop.
Git workflow for mobile development
So, we started using gitflow workflow with our server side as well as mobile development. It works out really well with server side code, since there is test coverage and with build automation, feature branches get merged into development branch as soon as they are tested ok. Unlike mobile development, since the changes are live as soon as you wish to (no time to deploy apart from build and testing), you can quickly test if there are any bugs in code you pushed and quickly make changes. So this workflow works out really great for server side development. However we are facing issues with mobile development with this workflow.

Now there are two major issues that we are facing with this workflow. One is that suppose we merged some feature into development and later figured out that there are lot of bugs in it. Now it can’t be pushed further, whole development cycle is stuck because that code is already merged with development. This is the reason we started forking feature branches from master rather than development as at least individual feature branches will have fully working code. One way is that each feature can be separately distributed to team members to test and only then will be merged to development but it's very cumbersome

Another problem is since base code with every feature branch is from master branch and it has to be merged with development, there are lot of conflicts. Earlier when we used to fork from development, we used to regularly merge development branch with feature branches so there were no conflicts but can’t do that anymore. So now to fix conflicts, we create another temporary branch from feature branch with which we merge dev code, fix conflicts and put that as pull request which is again little cumbersome.

Is there a better workflow for mobile development that people have adopted or even some practices that can be followed to solve these problems?
It's annoying that the article doesn't actually explain why they are getting out of the 'warbot business'.

'The big buys are over' does not explain why it is a good time to sell the division. If it's true, then it would be a terrible time to sell off a division since you'd get very little money for it. Presumably Arlington Capital Partners think that it is a good business to be getting into, even with the associated chaos and confusion that's inevitable when a company sells off a division of itself.

IMO it's also unlikely to be a reputation issue either - not many people know that Roomba also sells to the military, and besides, their robots aren't exactly killbots, they are saving the lives of their users. If anything, it should be a positive role.

Perhaps it is because the company wants a single focus? But even then, if a division of your business is large enough to sell and survive on its own, then you should also be able to keep it and run it separately from your house-cleaning division, with no downsides.

The shared research and development of both divisions must be an advantage, but the news article doesn't even mention that selling the division would lose these advantages.

So tell us again, Washington Post, why is the maker of Roomba vacuums getting out of the warbot business?
Definitely.

Is androids java mess a good thing?
Shipshewana+Gift+Food+Craft+Show+Kicks+Off+Today
No one is saying that internet communication is bad. The application to describe is not "social media", it's using tools designed as social media services as organizational software.
Unfollow and hide posts. That takes care of about almost all of it. The last part is people with interesting stuff that you want to know, and insane ramblings; for them I don't have a good solution.

This isn't a facebook problem, I have done the same with Twitter and would do it with HN if I could.
My feeling for what went wrong for Nokia, which kind of chimes with what's here is that the problem is that they couldn't decide a strategic platform and stick with it. There was a lot of differences between the Symbian crew and the Maemo crew.

The prime example of this , for me, was the Nokia N900. It was their flagship phone, I got one in their store in London and within 6 months it was pretty much unsupported, as Nokia changed focus again.

Also whilst the hardware was good the software wasn't great quality...
> This is simply not true. Language package managers cannot describe the entire dependency graph of a piece of software because they can't handle things that aren't written in that language. For example, there are plenty of Ruby gems that require a C compiler and C shared libraries in order to work, but those dependencies cannot be encoded in that system. System package managers can describe the entire graph, thus providing richer information.

On the contrary, the system package manager has to have a simpler model, precisely because it has to handle multiple languages. A generic model is never going to be able to capture the ruby-specific details as well as a ruby-specific model.
Maemo was a more capable Mobile OS that iOS 9.x... that's an ... interesting... opinion. Care to provide some details on what you think makes that the case?

My experience of Maemo on the N900 was that it wasn't really very polished and needed development which it, unfortunately, didn't get from Nokia
Good enough to get it into the duopoly with iOS, beating everything else.
Well, that's just how life is. Empty and meaningless. Except for whatever meaning we create. So I find Kafka both reassuring and amusing. No matter how bad things are, I can at least console myself that I haven't become a cockroach ;)
Watch Red Eye Online Free Putlocker – Putlocker – Watch Movies Online Free
>a concerned citizen, approach this topic at the bar or the dinner table?

One argument is : Tell them how their software (games, anything with DRM) spies on their kids and can harm them for life (insurance, job prospects, etc). Present it like this: Companies determine kid has X,y, z trait, their names (just by being connected they can do this with math and correlating other consumer data) then that kid is filtered out of companies/schools that he may want to apply to. Note that universities/corporations can pay to use services to filter out applications using analytics. AKA your equality of opportunity disappears when they can know everything about you and screen you out.

Corporations buy and sell information it's in things like EULA's on videogames that they can collect and infer all sorts of things by how much time you spend on the internet and also track your location.

Another argument : Make it about repairing everyday things, and how IP law is making us wasteful/harming the environment by forcing "waste" model of consumption. Basically corporations are trying to undermine our everyday rights by using intellectual property and copyright laws... to con us out of our right to own products and have them made fairly because we're 100's of miles away from corporations we can't 'storm the gate'.

Say old ages you want to fix an engine or repair the car yourself, there will be all these bullshit IP laws in the way.

Check out the "DRM" coffee maker.

https://www.techdirt.com/articles/20140227/06521826371/keuri...

Basically they want us to rent everything perpetually never own it... I'd love to make a meme out of "You wouldn't repair your engine would you? That would infringe someones intellectual(or insultingly imagiinary) property".

You can think of better examples but they are radically all trying to undermine our ability to own and repair stuff by controlling our governments laws.

The best way to fight back is to find ways to humor and disparage it and at the same time point out the fraud, and find easy examples effect peoples lives, purposely push the envelope and imagine the worst as well because people aren't rational, so push their buttons and find whatever works.

Note this racket/fraud has been going on for over 100 years now.

https://en.wikipedia.org/wiki/Copyright_Term_Extension_Act#/...
Why not Clojurescript with Reagent?
Are you planning on having a javascript sundial? :)
Isnt it because Google is pumping millions of dollars into it?
If you choose to put preroll ads on your video. Thats not always the best idea when you're making videos for reasons of marketing, as he would be.
There are efforts under way to improve the standing of scientific programmers, for instance the UK initiative described in this post: http://software-carpentry.org/blog/2015/06/what-is-a-researc... .

There are now fellowships in the UK specifically aimed at scientific programmers: https://www.epsrc.ac.uk/funding/calls/rsefellowships/ . Even so, currently there no real career path for scientific programmers. Hopefully this will change in the future!
Possibly, making any sense of 'linuxy' or quality of Java irrelevant.
I think "raw" distinguishes something from the normal state in which it is consumed. For example, a raw Big Mac is not the thing that McDonald's want to give you, but it's an interesting thing to study if you want to understand how a Big Mac works.
> Of course creating first Maemo on top of GTK and after that switching to QT sounded weird and with Meego there was other parties like Samsung and Intel meddling around so they lost lot of steam in that transition too.

From my perspective one of the problems was that there wasn't just one major transition, but instead there were two. First was the GTK->Qt transition, and then just as that was stabilizing came new transition from Maemo to Meego which never really succeeded. I think the reason for the latters failure was that while there was a lot of reasons to be exited about Qt (over GTK), there was very little to be exited in Meego (over Maemo).
It's interesting that you got a positive outcome. I also thought about this solution, but I just assumed, that it would work like a fine on them. And if clients would simply be fined, then they could decide for themselves whether to be late or not. And would obviously frequently choose to be late. And that's not something I want.

Of course, it may depend a lot on how you put it. I guess your clients rather felt a loss aversion and didn't just get comfortable with late payments.
The EFF obviously is focused on one aspect of the deal, and I don't find their arguments about the other aspects to be convincing. For the economic benefits, they use the same form of argument that global warming skeptics and creationists do, observing that there exists people who disagree with the general consensus. The fact that they can name one researcher on both sides of the issue does not imply that we should dismiss that issue as "debatable."

The fact of the matter is that "the agreement would reduce 18,000 tariffs. Tariffs on all U.S. manufactured goods and almost all U.S. farm products would be eliminated completely, with most eliminations occurring immediately." [1] Furthermore, we can't realistically ask for the parties to go back to the negotiating table to try to improve the deal. This one was 10 years in the making, which is depressing, but does mean that it's basically this deal or nothing.

[1] https://en.wikipedia.org/wiki/Trans-Pacific_Partnership#Tari...
It's interesting that Samsung were in a similar position around that time (and also had Bada in the works at the time). But around 2010-2011 they just hopped on the Android bandwagon and went all in with it, and won big time.

Which reminds me, what's up with Tizen? Are they still trying to push it?
That is true for most games, yet people are still interested in the score.
Apparently Chrome + default android browser = all major mobile browsers.

No Firefox or Safari support yet.
By this you mean management would better understand how their extreme perkele is forcing those under them to lie, and they could construct a better view of reality through better adjustments of how they view those lies???

How about focusing on creating a culture where the people under you don't have to lie, who's jobs and careers, and therefore families, aren't threatened when they tell the truth to those above them?
Smoke crack for a while, your interest in computers/reddit/hackernews etc will fall away as something far more important to you takes over your life.
Wondershare Dr Fone 5.7 Crack Patch and Serial Key
"Smartphones are unapologetically devices for consumption"

I see. The author has never noticed anyone taking pictures with their smartphones.

And Snapchat is also pure consumption. Except that users are taking pictures (and videos). And modifying them. And transforming them.
Glad to know somebody else also recognising position:fixed problem. It's really a nightmare. Is it really difficult to understand for their product managers to see that blocking top 20% of user's mobile screen just to hang a navigation which serve no purpose whatsoever is not cool.
The irony in this article is, due to the lack of a sensible line width, it is much easier to read on a phone than a PC
Well it was build on top of normal Linux tool chain instead of Java, but it was really easy to use, responsive and had all the smart phone features of that day. Much better than Android 2.2 which was the hot thing then. Quite close to iPhone in terms of responsiveness and ease of use.
This is awesome, thanks =)
> Maemo/MeeGo was probably more capable than iOS is today

This is just a ridiculous statement.

The iOS security architecture alone is more sophisticated and capable than Meego was. When you add all the various Frameworks and Kits iOS is an extremely broad operating system that even Android can't keep up with.

> but Microsoft was the one who stepped in and finished the job

No. There simply isn't room in the marketplace for more than three platforms. And Microsoft having better services, better engineers and a lot more money was always going to take that third spot.
> They have ruined web design.

Ironically, the site itself looks super good on a smartphone. I didn't check the source (because I'm on a smartphone...), but it doesn't seem to have any CSS styling applied to it.
Hardware, software & management - I think someone is missing something fundamental.

I had an N95, I thought it was quite a good piece of kit.

What people never seem to mention is that the iPhone had a generous data plan, whereas I was paying by the byte.

That is a massive difference in use case.
> All GC'ed languages still have issues of ownership, especially if threaded,

This is not true. Ownership is only relevant in the presence of mutability. In a GC'ed language where most or all data is immutable, one rarely needs to think about ownership. In Rust, one needs to think about it all the time.

Rust is certainly a leg up compared to trying to write multithreaded C or C++ code, but that doesn't mean its approach is free of drawbacks.

Empirically, even in Python - a mutable-by-default language - I find myself rarely having to think about ownership. That could be an artifact of the kind of Python programs I find myself writing, though. I'd be interested to hear other people's experiences on that front.
Fair point regarding creation, specifically A/V content. What are your thoughts on the rest of the argument beyond that point?