skysight-inc/HackerNews huggingface dataset:
Imagine Swift becomes a wild success; everyone's writing everything in Swift. What will your reaction be when Apple again makes a "legitimate business decision" and leverages the success to the benefit of their company and implicitly disadvantages other platforms? Maybe they double up on Swift support on Mac and start shipping additional features first for LLVM/Clang on OSX. Will you brush it off again as an understandable move by Apple?

I think you would. I certainly wouldn't be happy with Apple for doing it, but I would definitely say it's understandable. Like you're saying, they're a business, they make business decisions.

The point I'm trying to make there is any problems that arise from this fall squarely on the developers choosing to embrace this new language. I'm not writing this comment to convince Apple to act differently. The original post didn't make those arguments to Apple. This is all directed at developers, trying to change THEIR actions and feelings.

So as a developer right now, given that you have a plethora of open tools and an open ecosystem, why would you choose to use a language where a company has the opportunity to manipulate you in the future? Why write libraries and provide support and do this work for free for Apple? Writing libraries for the benefit of the community provides some security in that no one except the community stands to benefit from it. You can go to sleep happy knowing that you're helping out your fellow devs.

Writing for the benefit of a community that is paired with executive power means that it can all be swept from under you. Your library is still helping your fellow dev, but it helps the fellow dev with OSX 10.12 more. Now you've contributed to Apple's bottom line. Was that your intention?

I completely disagree with other commenters in this thread that we have some obligation to be thankful for companies for putting out things with strings attached. I'm not a spoiled brat for not liking everything. These companies would be absolutely nothing without their developers. It's time the community sticks together and realizes the power they have. It's not unthankful to demand more. It's dangerous to get swept up in the excitement of new languages and to assume good graces. Look no further than what Apple has done to Webkit, LLVM, CUPS and more. First class on OSX, give back only what's not newest. Swift will certainly be the same way.
> Would probably make compiler writers' jobs easier if they just spit out errors.

If this is your preference, JSLint has you covered. Really, every JS developer should be using a linter and tweak it to fit their coding preferences.
Very creative. I love this kind of stories. The first interactive display, made by Sutherland IIRC, had no framebuffer (irrealistic price at that time) so the team had to stream everything to fit into the small buffer they could get. As I understand it, everything was lazy and in sync with the screen 'machinery' so there was no delay even with limited memory capacity. It felt like hardware haskell.
That's no longer the case; the runtime is now open source too.
$199? Wow. Xiaomi's IP cam costs around $30 and does all the same, except it's 720p.
I find that limiting a companies usage of available tools based on policy decision is a bad business decision.

Oh, I completely agree with that. I'll never forget a particularly frustrating conversation with a client who refused to allow access to their database, because we were using 'open source code that anybody could have changed'. That sort of thing – banning open-source software from your systems – is silly.

However, you've got to consider the default-conservative attitude of larger companies. In Apple's case for example, the breaking point seems to have been GPLv3 - this was when they started reimplementing things like Samba and removing copylefted software. And that's because the GPLv3 represents a real business risk – aside from the direct patent implications, litigation under it is sparse, and businesses don't like operating in unsure legal territory!
I accept that. Maybe it was a badly chosen example.
Wonderful. Words to live by :)
That's pretty much always.

We never know exactly everything we are doing at the gene level (when breeding) and food plants always have more than one desirable trait.
Crash Bandicoot was quite a technical feat, but also (perhaps less talked about) - a marketing feat. The series went to sell ~50 million copies IIRC and was also the best selling Playstation game of all time.
Help to Get Picture and Srcset Fully Implemented in Microsoft Edge
Would be great if someone reimplemented it for the web.
Since the answer to the blog post title is, in the author's opinion, obviously "We shouldn't", that is, in fact, a terrible title.

The submission title is not poorly editorialized, it's pretty much exactly the author's opinion.
Distributed Eternal Bash History
100% agree. And this goes for everything from server side, to games, to mobile to client side web. Some of my favorite web sites have gone from a 1-2 second load time to well over 6 seconds. And then they're sluggish after they load. It's sad.
Iterative cycles take advantage of the regularity of change. APIs shouldn't change once public, hence the emphasis on Big Upfront Design. However, change still needs to happen so versioning comes into play.

Personally, when it comes to APIs, you can tell those that have been designed upfront rather than iteratively; they are generally better IMHO.
I have two boys and the biggest discussion my wife and I have is whether I tease them and push them too much. Especially the oldest one who was born 10 weeks to early and therefore we of course for a long time were being extra careful.

Both of our sons have bruises all over from play because we let them play and challenge themselves and each other.

It's a tough balance but I think it's doing them a favor also compared to later on in life.
That image is very unpleasant.

I get creeps from fractals, but now my whole body is itching. Humans are weird.
First LibreOffice Apps Launched on Mac App Store
Good point. That's more precise summary of their credo and it's narrower than the "community".
Booyakasha When Big Data Meets Content Marketing
Since you're talking about my comment, i just want to make a point : i'm absolutely thrilled by Apple's announcement. I just hope they're going to go all the way in.

I also understand why people that have been disappointed by previous MS tricks start to raise caution signs. That's the only reason i quoted the embrace stuff. To remind people that sometimes tech companies have hidden motives to offer free candies. Not because they'll be reproducing the exact same strategies.
WebAssembly will make both irrelevant in a few years.
Imagine Swift becomes a wild success … Will you brush it off again as an understandable move by Apple?

I'm a bit unclear what you seem to think is lost under these circumstances versus copylefted software. Let's say Apple released Swift under the GPL. They would still be free to do all of the things you describe.

So as a developer right now, given that you have a plethora of open tools and an open ecosystem, why would you choose to use a language where a company has the opportunity to manipulate you in the future?

This is, as above, no different from the copyleft case.

So as a developer right now, given that you have a plethora of open tools and an open ecosystem, why would you choose to use a language where a company has the opportunity to manipulate you in the future?

It's extraordinary difficult to argue that Apple would be in a position to manipulate me as a developer if I started using Swift. For one thing, once the code is open-source – that's it. I can continue developing software using that language. If Apple decide not to release new features, and instead keep them proprietary, then the community is free to fork development.

More importantly, if it's important to members of the free software community, they are entirely able to develop capital-F-free software on top of Apple's release!

I'm really thankful for copyleft licensing and the amazing tools it's given us. But it's a vary complex issue, and I just don't agree that release under a license with fewer restrictions is necessarily a bad thing!
> I completely disagree with other commenters in this thread that we have some obligation to be thankful for companies for putting out things with strings attached.

Swift will be released under a permissive licence, which has literally no strings attached - you can use the software however you like. Unlike the GPL, which has a very explicit string attached.
6 Best Free Tools for Testing Website Performance
The article isn't arguing that there's not a drought, it's arguing that even in a drought Southern California wastes more water (runoff) than it consumes and it would be easy to capture and use it.
I see functions as tiny stepping gears and composition as the mental act of assembling these mathematical pieces of geometry.
Interesting. I recently wrote my thesis on Latent Dirichlet Allocation (LDA), it's worth checking it out. Without going into too much technical detail, LDA is a 'topic model'. Given a large set of documents (a corpus), it estimates the 'topics' of the corpus and gives a breakdown of each document, in terms of how much it contains of topic 1, topic 2, etc.
I wish I had time to write a decent post. Lacking time, I'll try to be concise. If you want to really understand the benefits of TDD, the best book I know on the subject is actually Michael Feathers, "Working Effectively with Legacy Code". It is rather dense and getting a bit dated, but by showing you what you need to do to improve legacy code in a methodical fashion, he provides the basis for learning how to do good TDD.
And 'hello world', the program that made the world much more amicable.
Pledges from Apple are worthless. One need only look to FaceTime as an example.
I agree completely, and, on top of that:

> Yeah, Apple definitely doesn't like copyleft. That's okay; lots of people don't[...]

A lot of FLOSS advocates don't either. Like BSD developers, for example.

Personally, I release all my stuff under MIT/ISC licence. Feel free to use it. I don't keep parts secret, etc. I just choose MIT because I feel that users can use the code however they please, and if they share back, it should be because that's what the believe in, no because of legalese.
This article sums up the problems I've seen with TDD first hand. I've never seen a team end up with a better design than they would have using the old maxim: "Think hard. Then code.". I'm sure they exist, but adopting TDD does not automatically lead to better design, that much seems certain.

Another issue with TDD is that it is incredibly difficult to reason about. In many groups, there are at least one developer sold on the concept, and when I voice my concerns with the methodology they immediately demand an explanation why I "hate testing", or alternatively preach about all the goodness of unit testing. Which of course isn't the issue at all. Many developers seem to confuse TDD and unit tests, and the supposed benefits of the former is very hard to quantify.
What is the need? I can only think of reasons it might be 'nice to have' if someone was giving me it for free - and even then I would think twice. What are the real broad needs it's solving for a lot of people? (serious question)
I don't see how all this 'advice' is less than hypocritical.

I keep hearing 'overshoot' your salary range when negotating by X... and then when this lawyer does it OP should suddenly "run, dont walk, away from this dude"?

Strange crowd ...
The point of this effort is to elicit change from these organizations. If having breaches "a few years ago" means never getting a star, why would a company care?
Well, they had two options: license Sun's Java or do as they please with the GPLed OpenJDK. If they'd chosen the latter they wouldn't have needed to pay a dime. Sun/Oracle place no restrictions in addition to the GPL itself when it comes to OpenJDK (in fact, the GPL explicitly prohibits any such further restrictions). You can do as you will with it.
It seems like it can also easily be extended to an architecture with 12 bit address bus. Simply extend the size of every instruction to two bytes, and use the extra byte to refer to a 12 bit instead of 4 bit address.
- C# did not become super dominant.
- The runtime was only recently open sources, and MS keeps on releasing more bits. Their goal is to clearly port the entire runtime to OS X and Linux.
Yay! Is HTML5 winning war on smartwatches yet?
Sorry, but the native apps are much more than some language or binary code.
yep a lot of the property is brought as a safe guard against the the day when the mob starts hanging people from lampposts.

Also I suspect lack of trust in the local stockmarket might have something to do with it.
EDIT: I'm wrong see below

> "I'm a bit unclear what you seem to think is lost under these circumstances versus copylefted software. Let's say Apple released Swift under the GPL. They would still be free to do all of the things you describe."

Absolutely not. GPL means anything you put out must be published. If LLVM and Swift are GPL'd they can't develop additions to them, ship them on their Macbooks, and not publish the changes to the rest of the internet.

This is what's happening right now with LLVM.
If they started charging a monthly fee to use the app enough people would stick around that they'd be able to buy a sizable % of all the liquor stores in the USA. How many, I don't know. That would make an interesting interview question.

Edit: gonna try it

My city has 500,000 people. I'm going to estimate there are 500 liquor stores here. So that's 1 per 1,000 people. The USA has 330 million people, thus 330,000 liquor stores.

A liquor store is probably worth about $50,000. Thus, they are all worth $16.5 billion.

Whatsapp has 800 million MAU's. If 2% of them convert to $10 a month paying customers, that is $160 million per month.

They could run that business much cheaper than the current one, so say 50 employees at $10k a month each. $500k a month. Double that for hosting and rent etc. $1 million a month.

Those costs seem way too low in relation to revenue so let's just bump that up to 50% of revenue. $80 million/month.

So $80 million per month profit. Or over 2 liquor stores per hour, 24/7/365. In about 15 years they'd own every liquor store in America.
How to Count Number of People Using Wifi Signal?
Ideologies are not binary -- they each have relative importance. I don't think for a second that the FSF places software freedom above human rights or even equates the two. You can be a staunch theft opponent; that doesn't mean you believe theft is tantamount to murder.
Yes, it is a VM, but not "VM as in JVM or .NET". "VM" in Bob Nystrom's article is used as a later sense. Hence the article mostly does not apply to WebAssembly.

On the topic of JIT, the whole point of WebAssembly (and asm.js) is that it is so simple that you don't need JIT to execute it. You can AOT it fine.
I'd buy this for my parents. Been looking for a software company that will do something like this instead of all the other crap that's out there. You won't believe the low quality crap my dad has been asking me to take a look at for their house.

If people got alternatives (decent software startups/companies), please post them :)
Friendship and authority absolutely do mix. One just has to always exist in the presence of the other.
> Copyleft is meaningless without Copyright. Apple created Swift, and thus owns the Copyright. As the Copyright owner, Apple can licence/release Swift or parts-thereof, as it chooses. Even if they did release Swift under the GPL, nothing would prevent them from also using a non-released version of Swift or from keeping certain parts/libraries in-house.

If swift is GPL, Apple cannot keep secret changes it makes on top of third party contributions.

If swift is MIT/ISC, Apple can keep changes made on top of third party contributions secret.
"Best stuff" depends on who "we" are...

Here are some other users who may feel they are getting the "best stuff":

Compiler designers, programming language researchers, or even CS students the Swift core is a fount of of information to learn from, modify, experiment.

Teachers whose school could not afford Macs. They can now use Swift on cheap Linux machines, and eventually on Windows.

...
It will sit on top of the existing JavaScript engines and APIs, so no new security issues there.
I would not use Apache Spark when the amount of data is this little. I have myself done this mistake when processing only a few gigabytes.

Take a look at this:
http://aadrake.com/command-line-tools-can-be-235x-faster-tha...

IMHO I think people abuse Spark and I would be truly impressed if anybody could write a Spark program faster then just a regular Scala program for processing this.
Apropos acceptable sharing of private data, I too felt the bile rise in response to this product announcement .. the idea that there are generations of consumers who are perfectly willing to have days and days of video of their personal spaces available with little oversight to a third party, well .. its just too much to bear.

I think that the reason its happening, though, is because of a failure of OS producers to solve a couple of problems: one big one is that people just don't like having to maintain a filesystem - and more often than not, don't understand how to do it, either. Another problem is that the OS vendors are asleep at the wheel and have let parties such as Dropbox and so on basically eat their lunch on area's that should really, arguably, have been features of the personal computer operating system world. Peer to peer should be a built-in feature by now. Distributed filesystems which allow full control by the end user: likewise. These should be up-front services of the OS, and not some back-end monstrosity which execution as a market force is leading, directly it seems, to people who just don't care where their data are stored, as long as they can see it now and then themselves ..

I hope we will see some response to this soon - certainly actors like the IPFS group (http://ipfs.io/) have some interesting approaches to the problem. I'd love to see the expectation of built-in, de-centralized, peer-based-filesharing to take off, and we can put and end to all these inter-connected violations of human rights otherwise dressed up as fancy Web 2.0 operations of value ..
If. All languages you listed need GC, which won't be in the initial version of WebAssembly. In other words, you won't be able to compile Ruby to WebAssembly any time soon.

You will be able to compile Ruby implementation to WebAssembly, but you can already compile that to asm.js. That is different from compiling Ruby to WebAssembly.
Plenty of competition in that market. I have used 3 different services. Airbnb does not benefit from network effects the same way that facebook does.
Bring WebRTC to WebKit
When the GPL was written, this kind of software wasn't very common. Now that it is, the FSP formalized the AGPL, which they recommend over the GPL for server-side software.
Sorry but without Apple a technology like this would go nowhere. Half the mobile traffic on the web comes from iOS and is significant enough on Desktop. And is there something Apple has done with WebKit to deliberately prevent a technology from being adopted ? They supported WebGL for example.
Came here thinking about visicalc. Important but quite a smaller impact...
Honest question:

The author mentions patents. What patents could their possibly be with Swift? There's a TON of information on compiler theory available. Would Apple have wasted time trying to come up with something new just to patent it?
Did they fix the issue I heard of where it uploaded those massive files to the cloud with no bandwidth limiting, effectively killing connections with a slower upstream?
If LLVM and Swift are GPL'd they can't develop additions to them, ship them on their Macbooks, and not publish the changes to the rest of the internet.

This is true if you redistribute the GPL code of others.

However, as the copyright holders, Apple are free to release their code under whatever license they wish, or to refrain from releasing it. They can ship it on MacBooks, and are under no obligation to release the source code.

You could argue that they couldn't accept GPLd submissions anyway, but since they'd require copyright assignment in any case it's a moot point.
Better to see someone working hard to provide for their family than with enough time to protest inequality or otherwise take interest in their political fate.

The main issue is that wealth is very unequal in China. That low level official making 5k rmb/month is pulling in 20, 30, 40k rmb in grey money. They have to stash it somewhere, and overseas is safer when the government can make you an example at any moment.

Also, there are so few investment option in the mainland that if you do have money even from purely legit sources, buying a house overseas is probably much more sane than investing in extremely bubbly local real estate or stocks.
Cyberattack cripples Canadian federal websites, Anonymous claims credit
Imgur browser in the terminal
How do a non developer build an app?
CUPS is owned by Apple. Mach, OpenSSH, OpenSSL & Apache are not copyleft. The success of Apple has nothing to do with the copyleft software they use, most code used by Apple has been based on permissively licensed code or written by them. The main software asset Apple has is Cocoa and Cocoa Touch, which are as far from copyleft as you can get. Apple could replace every piece of copyleft software they have left in OS X tomorrow and no mainstream news source would bother to inform of this. That's how relevant copyleft software is to the success of Apple.

Now if you say "open source has been an integral part on the success of Apple", I would agree with that. Still Apple owes its success to it's own code not to code from others. If taking open source code and modifying it a little was all it took to make a successful company, all of us would be millionaires.
47 Simple and Effective Zapier Automations
What an amazingly entitled post. Why would outside contributors call the shots? Its Apple's project; not yours.
I think he would have found threaded emails with labeling an acceptable replacement.
I remember seeing a really similar project a couple of weeks ago and I can't remember the name. Any help?
Oh crap, you're completely right. Good point.

The bit about copyright assignment is significant though. There is a way for Apple to ensure the community that they will not screw them over for embracing their language. I think it would be prudent for the community to ask for that.
Don't know if is that you need or not, but common lisp has available the package 'cl-sentiment', specifically aimed to do sentiment analysis in text.

https://github.com/RobBlackwell/cl-sentiment

Other packages that you could find useful are cl-mongo, for mongo no-sql databases, cl-mysql, postmodern (postgresql) and cl-postres (postgresql)

And for Perl you have also Rate_sentiment

http://search.cpan.org/~prath/WebService-GoogleHack-0.15/Goo...