skysight-inc/HackerNews huggingface dataset:
The electrical motors can be rewound, but it's definitely a process no one will be able to do on site - the motor would need to be sent off to a company that has equipment necessary to do it. Still, it should be cheaper than $15k.
Download from: https://www.youtube.com/watch?v=wXFaU1TWRWk
FuncUnit and Cucumber – a perfect combo for frontend testing
I think you raise a good point. In the UK local governments in South Yorkshire to run fibre (well, fibre to the cabinet) to ~98% of the properties in the area, costing £100m+ of taxpayer money.

It never got more than a couple of thousand subscribers out of the 1.3million people that it passed. It turned out that the large national ISPs would rather use their own infrastructure or wait for BT (the national telecom) to roll out their wholesale solution than have to have a special case for support, installs etc for such a small proportion of their userbase.

It got shut down and is now pretty much rotting in the ground.
There is also a sampling bias, people who have experienced problems with the car are more likely to hang around in online forums trying to share their experience.
Modern 64k intros typically use D3D or OGL but they still need to generate the meshes, textures and sound themselves. In the DOS days (mid/late 90s) this was no different except there also had to be all sorts of software rasterization code in there just to get the scenes rendered. OTOH there were plenty of effects done back then that were strictly 2d using clever lookup tables.

The DOS 64k intros typically didn't link to any stdlib but would just provide their own implementation along with a few of the symbols that the C/C++ compiler (typically Watcom) would require. Combine that with a tiny DOS extender like PMODE/W and a compressor like UPX and you'd be off and running. A minimal intro (just showing a bouncing pixel or whatever) could be had with only just a few kilobytes.

Nowadays intros typically rely on, as mentioned, D3D or OGL but also usually on the MSVC runtimes. Compression is still done using tools like UPX or kkrunchy but that actually's becoming difficult to do because virusscanners are usually flagging them as suspicious nowadays because of all the malware that also uses these compressors. Also, file size is not something that most people care about too much nowadays so the whole concept of the intro seems to have become less and less interesting over the years.
Bah, this was dropped on x86-64, so it's not very interesting..
It's an interesting idea, tracking people's current locations based on their sharing on social networks, and cross-referencing other databases to find out if someone is at home.

But this seems like a very high-threshold way to find out whether someone is home. I mean, if I'm really interested in robbing someone, am I really going to go through the trouble of searching through social networks, cross-referencing information from people in my area, and only then starting to figure out which homes are (and aren't) worth robbing?

And of course, there are a number of very important variables that such an analysis ignores: Whether the person lives alone (or is renting the place out via AirBNB), whether they're in a building or single home, whether there is a burglar alarm, how good the police force is in that city, how easy it is to get into (and out of) the home in question, and whether there's anything worth stealing.

So it's an interesting experiment, but telling people to remove their names and geographical information from Instagram to avoid being robbed strikes me as a bit far fetched.

I run an e-mail list for people who live in my city (Modi'in, Israel), and we now have nearly 3,000 subscribers. People are constantly saying, "I'm going to be away on vacation during such-and-such a period of time. Does anyone need a short-term rental?" That strikes me as a far greater invitation to mischief and robbery than Instagram or any other social network.
Can't agree more.

The problem is not the language itself, rather who uses and whats the culture associated with it.

Java is mostly used in the enterprises, where unfortunately thest "architects" exists. Architects are nothing but people have grown out of the roles and in a way of organization recognizing the peoples talent. Most of the times the Architects are redundant.

Most of the cases use of Java is nothing but writing your business logic into the Java code.

Unfortunately, architect to justify himself would try to engineer a solution, which never needed engineering itself. and down you go in the rabbit-hole of oops and abstraction.

Unfortunately it will be pretty hard for Java to shake up this image.
I had a bike and a DeWalt cordless drill stolen from my garage.
$13 Mi band tracks steps and sleep as well as unlocking your phone
>> 8x oil change

what? Are you changing your oil every 3.5k miles?
Actually there are "real systems" being written in FP e.g. Clojure @ SoundCloud.

They just aren't architected the same way. Instead of a monolithic WAR you end up with a series of micro services. FP is actually more suited than OO for micro services since it naturally forces developers down the "do one thing well" approach.

So I would stop with the "OO is what real people use" nonsense if I were you. Because languages like Scala and Clojure are rapidly taking over from Java in the enterprise space and you may find yourself on the wrong side of history.
The real problem is developers not understanding Object Oriented programming. Many developers write procedural style in Java or any other OO language. So you get God classes, methods that are hundreds or thousands of lines long etc - I'm sure we've all seen those horror shows. It's just a lack of education coupled with a culture where there is no strive for technical excellence.

You need high quality developers in Java, just as you do in any other language.

It seems like the article's beef is with OO programming, not Java per se.
It's not on the page you link to and I don't recall ever seeing it in the UK.
GIANT BUG... causing /usr to be deleted... so sorry
I think it's far more interesting and productive to use facebook posts for this, rather than GPS coordinates in EXIF data and comparing it with a phone book (which is essentially what they're doing, according to the about page). Facebook posts often contain much more information and that information is easier to extract.

Realistically speaking, neither of these cases will be addressed. Although properly using the privacy settings can help, the entire reason people use tools like these is to express themselves about things they're seeing, and that usually doesn't happen at home. This coupled with the fact that the risk is extremely low, and that there are much better ways for a burglar to obtain this information, I don't think this is the best way to go about privacy awareness. It was probably fun to build, though.
2 Day Diet Pills Official Site  100% Original 2 Day Diet Japan Lingzhi Pill
Official Site Authentic 2 Day Diet Japan Lingzhi,High Quality with Wholesale Price,Lose Weight Safely and Naturally at here With Free Shipping!
Agreed -- if your logical/programmer side interprets <2 as ==1, then be careful with your code refactoring. :-)
And which got a huge amount of publicity about it.

http://techcrunch.com/2010/02/17/please-rob-me-makes-foursqu...

http://www.telegraph.co.uk/technology/twitter/7266120/Please...
ClearTax giving away Bitcoin in India
Been there done that.... http://pleaserobme.com/
> OO actually works well for scaling complexity, much better than toy immutable functions do.

Sure, but the problem is that OO is frequently applied where you don't need scalability, and then OO becomes the complexity that needs to be scaled.

A low-hanging example of this is the singleton pattern, and the Wikipedia section titled "Example of use with the Abstract Factory pattern" saves me from having to bother making the point any further: http://en.wikipedia.org/wiki/Singleton_pattern#Example_of_us...

It is my fervent hope and wish that all programmers someday accept that there is no universal methodology, that FP and imperative and OO all have their place and their faults, and that it is OK to sometimes not use one of them somewhere.
FuncUnit is an interesting concept to me because oftentimes I find little value in Unit Tests and great value in Functionality tests, yet the path of least resistance to implement Functionality tests is usually Unit Testing frameworks.
Yes modern smartphones often hardcode ntp servers and prob do ineffective hard resetting. Would be good to know more how they do it.
Good architects play a vital role in the organisation especially if you have a sprawling set of agile teams that don't necessarily work together.

There are plenty of really tough integration, security, scalability and performance challenges that need someone who is across the entire stack from very top to very bottom. You rarely find developers who can manage it all and still find time to cut code.
It's not really a protection though. With a jailbroken phone you could probably change the key with a hex editor or similar. There's also this: https://github.com/iSECPartners/ios-ssl-kill-switch

Also, you're totally screwed if you need to reissue your SSL cert for a security problem (think heartbleed). You'd have to reissue the cert, wait for apple to approve the update, then hope that a significant proportion of your users actually update your app.
> I've found a few ways of doing this that work for me, and I can post some of what's worked if anyone's interested.

If you have time, please do :)
20 Content Marketing Mistakes To Avoid Like The Plague
great article and love the idea of the comic strips!
What could possibly be done in the React.js version to make its performance closer to Mercury/Elm? I notice some 'shouldComponentUpdate' methods are already overwritten.

Or is this the limit of an overly mutable language like js?
You may not do this for say, robbing joe blogs. But what happens if your going to rob a celeb who has 50k+ of jewlery in their house and you know they're going to be out of town filming for three weeks, or that they are doing a PR night so you have 8 hours before they return.

There are examples of this, popularized by the movie The Bling Ring[1].

[1]http://en.wikipedia.org/wiki/Bling_Ring
Assembly, and Low Level Coding is the exact opposite of solving 'real' problems. Your going low level to create problems that didn't exist, as opposed to working on the core issue(often business related) your software is trying to solve.

Languages should allow you to focus on creating software that fixes a real world problem, as fast and cleanly as you can. That doesn't include bit flipping, or bit operators or anything like that unless required.

People should be working in super high-level languages like Haskell, OCaml, F#, Clojure, or languages that fit their domain perfectly. The goal is to fix problem the as concisely and quickly as possible.
It should (and the the previous PleaseRobMe.com also made this mistake) use the word "burglary" rather than "robbery". Edits - this could just be a British difference rather than a US one, if so, my bad!

Robbery is about theft (usually using force) from a person, whereas burglary is unlawful entry to and theft from that person's property. Since the person is not going to be there, the property is empty and ripe for burglary.

A more interesting and challenging PleaseDontRobMe would focus on where the target is, away from home securities, who they are with, the security situation of the country, the best escape routes relative to their location, locations of police, CCTVs etc. Much more interesting geographically in my opinion!
100% authentic and original Meizitang Botanical Slimming Soft Gels
Buy 100% authentic Meizitang Botanical Slimming Soft Gel. Meizitang Botanical Slimming Strong Version Diet Pill - www.meizitangbotanicalslimmingsoftgel.com
There're a lot of comments saying thieves are too thick to use technology for robbing people. Maybe some are, but there are plenty of tech-savvy people with no scruples who might use information like this. To-order car thieves use plenty of technology to do their business, for example. And furthermore, I'm sure we all know plenty of houses that were mysteriously robbed at an opportune moment (the night everybody went on a trip, for example).

Thieves mightn't be cross-referencing databases using various API's, but they're not so thick as to miss opportunities that might present themselves through Facebook posts etc.

I don't see a problem with increasing awareness of the possibilities.
Interesting! The most important difference between frameworks and libraries seems to be the "don't call me, I'll call you" pattern. Frameworks call your code, while libraries get called by your code.

It's easy to see why "don't call me, I'll call you" leads to unreadable code. A piece of code is readable if you can understand how it works, not just what it does, and a big part of "how it works" is figuring out the control flow. Inverted control flow makes code less readable, regardless of any other benefits it might have.

Viewed in that light, it's hard to see how moving to better languages like Haskell would solve the problem. Functional programmers pass functions around all the time, so a lot of functional "libraries" are actually frameworks that insist on calling your code in complicated ways, making it conform to very precise types required by the framework. There's certainly no shortage of abstraction in Haskell code. As a result, it seems that most Haskell programmers don't even try to understand the control flow of their programs, because it's almost impossible.

I wonder if we could have a principled approach to programming that discourages the "don't call me, I'll call you" pattern, and encourages code that you can simply read from top to bottom. Do this thing, then do that thing, then do the other thing. It would probably be unlike anything that exists in academia today.
Really? Which regulations in particular do you feel it would be awesome to do without (apart from KYC/AML)?
But worth noting it is only ±1 ms accuracy which is not useful in many applications.
Isn't it on all the cans? http://lmgtfy.com/?q=coke+cola+can
Blame the 90s : the Gang of Four design patterns book, UML, et al.

If you wrote code that did not abstract enough, such as not using factories, it was jaw-droppingly obvious to your colleagues that you were not good enough. FP and Scala owe the sheer verbosity of Java a lot for their current success :-)
Is "responsive" the new buzzword for "things that change when you resize them"? I've been seeing it used an awful lot in web design as of the past few years, often rather vaguely as some sort of feature.
I think this code truly represents the essence of this article:
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
My TV is 37 inch, trying to haul that in the street should raise some eyebrows. And it doesn't have that much resale value.
It always surprises me people think this is a real issue. For many "victims" a more effective algorithm would be something like this:

If victim's age > 25 && < 60
If hour of day > 10 and < 17
Rob house

That algorithm will fail in many cases of course, but I'd argue it covers a much larger number of people than the supposed problem identified here.

For added safety, the implementor may add this feature prior to the "Rob house" step:

Knock on front door
I like this a lot. I've long considered that "As Customer A" or "As a User" thing can lead to user stories being quite difficult to read, particularly if designing anything to do with collaboration, even more so if there are multiple users of the same type.

Like you, I also name my example actors. When Dora the Developer wants to run a screensharing session with Peter and Patricia the Powerusers, the narrative is much easier to follow. Using cartoons is an extra step in that direction.

One thing that worries me about the use of cartoons is that it offers an extra opportunity for unhelpful bikeshedding, even before the features of the actual system are considered:

"There aren't any women in that department, can you change Sally the Saleswoman into Simon the Salesman?" (followed by "there aren't enough female characters")

"There aren't any East Asian characters - Can we make Ahmed the Accountant Japanese?" (followed by "Can we just make everyone white? I don't want to offend people with stereotyped caricatures")

"We should put Brian the Blind User in a wheelchair, to show that he's disabled"

Have you experienced that at all?
Let's wait and see if Om inspire others. You know that ideas take time to diffuse, OOP/MVC has been a somehow natural fit for IHM, but like many other ideas (closures?) now that people can see it, maybe they'll change their mind.
Well at the moment, yes, but we'll have to wait and see until the Model S and co are > 5 years old, or even >8 years old and the warranty on the battery expires, or other age-related issues crop up. I'm thinking it'll be a very expensive used car to keep on the road, which will limit it to collectors or rich people and/or severely impact the resale value.
> Stability -- none, regarding possible law suits from Oracle. Yes, it does matter for a company. Yes, Oracle did that in the past.

Do you have actual examples of companies using Java for their run-of-the mill software that have been hit with lawsuits from Sun/Oracle? The only two I can remember are Sun vs Microsoft (because of proprietary extentions) and Oracle vs Google (complex licensing issues).
Sounds like FUD to me.
Presumably it's easier to rob a house at night. If someone is away, you can do that.
What Harry Potter Taught Us
I don't see any reason the software update process needs to be more secure than the firing process, and presumably these batteries can be fired remotely.
Do I get this right? You can not upgrade a server cluster to the next version of the operating system without complete new installation??? Could you please write something about these kind of things, this is very interesting!
http://en.wikipedia.org/wiki/Eugene_Water_%26_Electric_Board has worked pretty well to provide water and electricity in the town I grew up in.
It's unfair to focus on "UI frameworks" when UI frameworks are specifically aimed at supporting client OSes where they have to deal with "preferred frameworks", all of which were developed when OO was all the craze. Functional programming has only been discovered as a practical paradigm quite recently! Besides, implying that "big serious programs" necessarily implies that they are UI programs is completely wrong.

Unsurpisingly, if a given JS UI framework is OO, it is not OO in the traditional sense because JavaScript itself is not OO in the traditional sense. If you make a framework, you use the language of whatever runtime you are targeting.

Functional programming is often used to write server code that must easily parallelize and scale across cores, CPUs and clusters. Mostly because the FP paradigm is more obviously advantageous in that setting, but also because those services have less baggage of trends than UI heavy programs do.

So you are arguing that there is some perceived evidence for OO in UI programming, but I think that could more easily be attributed to historical trends. Note that I'm not necessarily disagreeing with your conclusion, just that your reasoning is flawed.
The classic logo is often on the can/bottle near the nutritional information: http://imgur.com/OHinuge (from a can of Diet Coke in the UK, taken today. The can was part of a large multi-pack case).

There's a little bit about the history of the logo here: http://www.coca-cola.co.uk/125/history-of-coca-cola-logo.htm...
> while allowing non technical stakeholders to write
> feature definitions.

This is why we can't have nice things.
The main advantage is when doing something like this is Haskell the code you pass around can't have arbitrary side effects, so you don't actually need to worry so much about where it is called.
Most robberies happen during the day when people are in work and streets are noisy. Attempting to rob city house in night sounds like even more stupid thing then daytime robbery.
DrawElements acquired by Google
Periwinkle may be invasive but it's also easy to control, similar to English Ivy. It does great in shade and is an attractive option to plant (or allow to self-propagate) under large evergreens ... as an alternative to doing nothing and just having dead grass there like most people do.
> Because languages like Scala and Clojure are rapidly taking over from Java in the enterprise space

Let's see how much of the momentum these languages keep after Java 8. Default methods, the new stream API and lamdas provide much what most developers need without introducing baroque features and orthogonal infrastructure.
It might be easier to burgle a house during the day, when the target and the neighbours are more likely to be at work. Anecdotally, my house was burgled around 3pm and my friends was also burgled whilst at work.
> The other proper answer is to have a good backup and recovery system.

And, of course, that should've been the solution to OP's incident with the Korean Airlines flight 007. Backups, surprisingly, are scarcely mentioned at all in this whole thread.
>Because that's what people use to write real programs.

Many people said the same of GOTO statements a generation ago.
Pixel Perfect: Fingerprinting Canvas in HTML5
$13 fitness band – first wearable from Xiaomi
Ish. It is the buzzword for "the same design works on a vast range of screen sizes and orientations".

The fact that things rearrange dynamically as you resize your window on a desktop box is not the main target, the target is a design working equally well on your desktop, your table in both landscape and portrait, your much smaller phone, and so forth, so the designer doesn't need to maintain multiple versions of the site/page/app.
Between 60%[1] and 75%[2] of burglaries occur during the day.

I've been burgled before. They dressed up in white "painters" overalls, carried some tools and no one asked anything. Broad daylight, broke the door.

[1] http://homesecurity.lifetips.com/faq/139392/0/do-burglaries-...

[2] http://www.apartmentwiz.com/houston_apartments_information/w...
Tower 2
> Is "responsive" the new buzzword for "things that change when you resize them"?

Not just change, but remove flourishes and not entirely necessary elements.

> I've been seeing it used an awful lot in web design as of the past few years, often rather vaguely as some sort of feature.

It's a feature for cross-device compatibility, the point being to alter visible content to fit multiple device sizes.
I prefer "responsive" over "things that change when you resize them" because it's way shorter.
Perhaps this could be better used as a heuristic for delivery companies to select a delivery time?
None of the results on that page or image results show Coke in the classic font.
That is "The Hobo’s Method" according to Ilya Pukhalski (source: http://www.smashingmagazine.com/2014/03/05/rethinking-respon... ) and I totally agree with him. That is not efficient way, even lazy way of creating responsive logos. The svg for each logo is repetitive and contains each logo variant - simple sprite technique is used and that is completely not innovative. The same effect could be achieved using png image. Only advantage is that svg saves some space.

It would be much more impressive to see the same parts of logos reused on different variants of logos - "The Man With A Gun’s Method" that is covered in the same article by Ilya Pukhalski.

For comparison:
"The Hobo’s Method" - http://responsivelogos.co.uk/images/logo5.svg and "The Man With A Gun’s Method" - http://pukhalski.com/responsive-icons/responsive2.svg

Edit:

It is strange that author publishes (source: http://www.joeharrison.co.uk/projects/responsiveicons ) the information from Smashing Magazine containing the methods of responsive SVG and still uses the poorest method.
Car theft scenarios:

- look on instagram for nearby recent photos of fancy cars to steal

- visit neighbourhoods where rich people live and look for fancy cars to steal