skysight-inc/HackerNews huggingface dataset:
> has perf issues with angularjs

> writes a solution using jQuery

Angular tries to be clever and solve loads of problems, sure tables and table rendering sucks anyways, but a simple querySelector with jQuery is 98% slower than just using normal DOM methods.

If you're gonna write your own bits of code to improve the caveats of any framework, especially in the financial industry, you go full hog and you write it properly.

Fixing an angular problem with a jQuery solution will get you marginal gains. Fixing an angular problem with a DOM solution will get you the best results and it isn't even that hard.
Wasn't the Ricky Gervais Show really podcasting's first breakout hit? It got a Guinness World Record and ended up becoming a TV show in both the UK and US.
I don't understand this. Were they using angular grid? Because I work on an app that has tables with ng-repeat attributes and it is insanely fast. It loads hundreds or thousands of rows into about 200 columns that are separated by tabs. The client side filter searches are instant.
Judging from your username, I feel like I've been seeing you on various web forums for ages. At any rate, yes, yes and yes. It doesn't take a CS wizard to see such basic faults from the get go. Still I had to try angular for a day to really see how terrible it was in practice.

There is the adage that "good enough" is good enough, but there should be another one that starting really bad stays bad no matter how many fixes get applied year after year (then the magical 2.0 happens)

Look at good enough languages like Perl and Python, they have their faults, Python 3 solves a lot of them, but 2.7 stays in production because it really is good enough. People don't go bailing on it for some other option because their codebases got unmaintainable, performance problems got O(n^2) or worse, they just go bail because maybe they want to try the compiled ease of Go or maybe touch Julia over numpy here or there.

Bad is bad, and people need to use just a bit of their algorithms class to figure it out. Shame that a ton of people asking similar questions about "how do I _______" results in a higher PageRank, while time tested easy to use options just hide in the shadows of good documentation and infrequent code updates.
A little OT, but I have to say it: "Photo Credit Google Images" does NOT make it OK to use copyrighted material. Google can claim fair use, you can't.
Bizarrely enough, I've built about 4 web apps ( using Angular over the past 2 years also. However, I've found that scalability (mainly due to it's reusability) is one of the strongest points. I've worked with enormous applications built entirely with jQuery.

I love angular, but perhaps thats because I'd only worked with jQuery before.
In the case of the general public it is different. A curtain is a highly intuitive instrument for privacy protection, you pull it and it covers the window. Understanding how to secure a technical device such as a webcam is not as easy or intuitive, especially if as another poster mentioned, the device is configured to broadcast automatically. People will almost always stay with the defaulted configuration unless they fully understand the technology, hence the reason wifi routers now come with long cryptic random passwords.
My guess is he's using lock-free data structures + a lot of cleverness.
I am sorry but that is an awful comparison. Nothing about the two can be compared except the occurance of death. Also there is no conspiracy in Serial.
A while back, my workplace had a medium-sized disc array. That is, something like a hundred UW-SCSI 72GB drives, arranged into about twelve different RAID-5 sets. When we had to power it down because of scheduled electrical work in the building, about eight of the drives failed to come up again. It's a miracle none of the RAID-5 sets were broken. Hard drives don't like being switched off if they have been going for a couple of years.

And that is why RAID is no substitute for backups, people. A reasonable proportion of events that will take out a hard drive will take out more than one.
Lucky you, in the old days we couldn't always re-render whole scene :(
CodaLab Demo
"Trying to learn the framework by reading blog posts isn't going to work."

"...but if you Google for ngRepeat performance there are tons of discussions on this."
Modern flush toilets originated in the UK, where water is in plentiful supply. It literally falls down from the sky, with depressing regularity.

Yes they're not very good in dry climates, but they were never designed to be.
So what's the point of root? To keep me out but let malicious people in?
Design Details: Android Lollipop Part 1
That's not what I'm saying. I can't make it much clearer than:

a) suddenly out of the blue, a Ford Transit mutates into a toaster.

b) someone is "pretty sure it is related to the impending comet impact".

c) Everyone goes YAY SCIENCE!!!

Sorry but derision is the only thing left. It's not science, it's religion.

a) suddenly out of the blue someone delivers a load of fish.

b) Some guy doesn't notice this and goes "pretty fucking sweet; I'm totally wasted on mushrooms and I reckon that bearded dude over there turned that loaf of bread into all those fish. Damn I've got the munchies."

c) HE'S THE FUCKING MESSIAH.

There is no causality chain established other than a hunch.
There's a sort of disconnect between stuff that's part of the machinery of a house and the tech gadgetry world.

House parts like central heating, taps, toilets and such tend to be very standard and long lived. How long did indoor toilets take to get traction? How big an advantage are indoor toilets over chamber pots?

A "gadget" is very flimsy feeling compared to a toilet. IE, I expect the toilet to work in 20 years, but not an ipod. It might get clogged, but any plumber will be able to fix it. I think people are hesitant about installing ipods as part of the core infrastructure of their houses. What happens if your windows system won't connect to a router you buy in 10 years. Who will fix it? What happens if wifi becomes obsolete?

I don't think I'm explaining this very well. Merging gadgets with houses is kind of unnatural. They operate at different time scales. Tortoises and fruit flies.
Smart home or the whole Internet of things stuff frightens me a lot. Not that I'm in fear of privacy implications of interconnected devices and the bad and insecure software. No it is just that the smart stuff is out-dated pretty fast and increases the amount of (toxic) waste rapidly. And we are already fighting for rare earths and other building blocks of these devices. So we are not just replacing our TV or notebook every 1-2 years. No, now we should replace all the gadgets that are advertised to make our lifes easier and safer, if it is your freezer, your smoke detectors, electrical outlets, body sensors, thermostats and everything else which can hold a chip and has a excuse to be "smartened".

No, I do not want that.
The other half being providing a service they find worthwhile that doesn't change at every whim.

Taken to the other extreme, a constantly breaking Github doesn't have any value proposition.

Promises are not always explicit and not at all related to laws.

The next Transformers being something to look forward to is a promise, but that doesn't mean not liking it is in any way wrong or that I could sue someone for it. I can choose to leave the movie and never go see one again. The producers of Transformers certainly owe me nothing, but they also cannot tell me how to feel about their handling of the material.

Github promises the most awesome code hosting around. That's a very different thing for many people. And to some people you can live up to the promise, to some people you cannot and it's perfectly fine for those to feel let down. Calling all those people "entitled" is, quite frankly, insulting.

As I said: putting this like it is the end of the world is overreaching, but it is a valid complaint and a valid sentiment. Saying that this is the most important thing on Github, because it happens to be specific your problem is entitlement.

Finally, it isn't true that you are only bound by spelled out things. The law many people cite so often has the concept of Good Faith: http://en.wikipedia.org/wiki/Good_faith_%28law%29 and similar fun things that extend beyond that. So Github _does_ owe me beyond their ToS.
(I appreciate that this is probably not a case covered by this)

It's a common sentiment in these circles that only the rules written on the contract are the ones that count, while nothing can be further from the truth, widely varying from legislation to legislation.
At one project I worked, someone created a bug "system will stop working with the end of the world on <last popular End_of_Word prophecy>" (yes, it was a joke)

Fortunately the bug was closed.
I think you've nailed it.

The reason these products don't focus on people is that people are hard. Hiring is one the hardest things out there, with often warped incentives on both ends re: honesty. Building a product/service to solve this dilemma in a way that satisfies all parties is probably even harder, and then on top of that you need a business model for pulling dollars out of the matching process.

It's much easier to just build a product that matches technology stacks, and it's not immediately obvious that it's the wrong approach.
I usually combine sharing what I can with showing my credentials (I've a PhD and can share the work I did for that, which I don't put on GitHub because it doesn't feel like the place for it), as well as share anecdotes and get others to vouch for my ability. I've found actual credentials are the best help, but your mileage may vary.
yeah, still don't see where he talks about architecture. He explains how memristors can be used for logic, but con Neuman is not implicitly wedded to transistors.

Don't get me wrong, I think they will be useful.
But you still hit on a useful point: that is, many "solutions" intended to improve design simply move the problem around. I first noticed this when Hibernate became all the rage, as well as some webapp frameworks.

They were supposed to be awesome because they didn't require code. Looking closer, they'd just replaced code with declarative config files that spread a given piece of functionality across multiple files/formats that were sometimes harder to debug.

Each layer implemented comes with additional complexity, not less. The real solution always seems to come down to simplicity and minimalism. To my mind, it's always seemed that limiting the number of technologies employed is a useful goal.
Female programmer here.

Some of my favorite toys were Legos. My little brother used to get all the Lego presents growing up (because he was a boy) so I would use my allowance to buy my own. When she's old enough, try out the Lego Technic series or the Mindstorms. I had the entire first-gen of Bionicles (this is where my allowance went for a year), a Mindstorms R2D2, and the RCX 2 Mindstorms kit by the time I entered middle school.

I don't think you'll get a lot of mileage with the prepackaged science/engineering kits. I used to get those all the time for presents. Barely used them. They're just not that fun and don't have a ton of reuse. You also get seriously railroaded. You want to explore at that age, not follow a set of instructions.

Same goes for telescopes. The kind that parents are willing to buy are the kind that will probably get used only a couple times (unless your kid is REALLY into space). Also applies to the star-projector things.

Set, the card game. What a great game.

Equations is a competitive math game for 3rd-5th graders. You can scale it for lower grades by taking the exponents and square roots out. It's best played amongst peers. Get the rules off the internet, not from the boxed instructions. I was pretty good at it back in the day--my team placed 3rd at regionals. I volunteered with my old elementary school's Equations club a few years back and whooped those kids (still got it, baby). ;)

I think early access and training in hardware tools can really open up the possibilities for any kid that likes building things. I was always building things as a kid.

EDIT: Punctation and details.
> Keep them private and competitive.

Hah!
12 FREE Holiday Fonts for Your Designs – BOCO Creative Blog
I wanted to get a video baby monitor for my twins, but gave absolutely no thought into getting an internet-connected one. I just didn't see the benefit and it seemed super creepy having the camera accessible over the internet.

Now, after about two months, I realize that I hardly ever use the video feature and the audio is almost always enough. I guess we'll see if I change my mind as the babies get a little older, but I'd rather have my $250 back and just have gotten a simple audio monitor.
Sorry, did I miss the part where the author explained the "right (tm)" way to do things these days?

Seriously though, I've used Angular just as long as the author and for the most part I wholeheartedly agree with the complaints (and I have complained myself for some time). However, what is the "better" way? People keep throwing out things like React, but React solves much less for app developers. Also, that answer doesn't help the countless people who began app development more than a year or so before React was released.

The Javascript ecosystem is evolving constantly and yet in some ways not much at all. Throughout that time, I've found that just about everyone can find excellent reasons not to use the various frameworks and libraries but few offer concrete recommendations in exchange for these criticisms. It's disappointing.

At this point in our own project, like many others I assume, we are reconsidering Angular. Not simple because we don't like it, but because clearly the Angular team doesn't either. Angular 2.0, like Sproutcore 2.0 before it, appears to be a complete rewrite. (Rightfully so.) As a result, we plan to examine our other options in detail while our work is still mostly in the prototype territory.

Right now however, I don't think I've seen anything yet, that makes sense for most people who've started out with Angular to do that re-write. I'm hoping as I spend more time examining this I'll find I'm wrong.

I've had many people ask me what framework they should use for new projects and every time I've said, it probably doesn't matter use right now, but be prepared to fully rewrite things in a year or so. The JS ecosystem is in so much flux right now that you can't count on any of these choices being the right one in couple of years. I've accepted that reality for now.

People hate this answer. They tell me that no PM/Exec is going to want to hear that. Fine, don't tell them. The silver lining is that whatever does comes to save us will hopefully be so much more productive than what you were doing before you won't care about rewriting it, you'll do it because it actually makes sense.

Let's all hope that's true.
What your car could look like in 2030
Also you can use a different exotic approach in every game - it's completely open!

In the modern closed web you unfortunately have to deal with legacy tech like HTML, JS, CSS which will never ever go away "because compatibility".
IE11's developer console UI is also apparently written in HTML/JS rather than a native UI. It's not better.
So if not Angular then... what? If I wanted to do a single page app with REST backend (little to no db access), what would you recommend?
Honestly, the problem is not just that the Nest thermostat and smoke detector are expensive... I could (almost) justify spending $200 on a thermostat or smoke detector once. But I have 9 heating zones and approximately 9 rooms that need smoke detectors. You know what I'm not doing? Spending $1800 on thermostats for my house. Hell, I haven't even replaced all the old spring-loaded mercury-filled thermostats from the 80's when the house was built. If I could buy one Nest, and 8 remote receiver thingies for like $10 each that just report wirelessly to the Nest, then I might actually buy one.
Scala OOP Galore
They do: https://gitlab.com/gitlab-org/gitlab-ce/. They maintain a Github mirror to allow for easier contribution. Github is more than just a version control software; it's a community.
AI is a tool, not a threat
On Chrome v37, if you change the theme, the "Download Now" button breaks.

A lot of the UI elements are really great, especially the Views section.
I used to be part of a forum that had a massive list of the default login and unprotected cams. There were maybe 10k-20k per document, maybe 5 or 6 documents. As far as I could tell, all were working cams but 99% of the time there was nothing happening. Either they were too dark to see much, pointed at a front door, or showing rooms with no one in them. I personally never saw any movement on any of the cams except for a sleeping puppy.

On the rare occasion someone found a not-empty cam, there would be screencaps immediately. It was like crowdsourced voyeurism before crowdsourcing was a thing. The best one was a guy who was using the camera to monitor his weed grow op. Apparently, according to more knowledgable users on this forum, he was using the lights inefficiently. It sparked a massive debate on the intricacies of grow lights and that's when the thread died.

It was creepy but far less creepy or exciting than I imagined when I first stumbled upon the thread. Still, change your passwords people.
Entirely agree!

But blaming everything on climate suddenly isn't the right answer. Perhaps someone lost a ship load of PCP in the sea and they just snuffed it. And they're trying to hide that.

Another hypothesis that could be tested rather than "fuck blame it on climate so we can get some funding and get some nice new Herman Miller chairs and a new MacBook each"
Author of the article here.

Ironically the first draft of this post hit a lot more on the point that the mere concept of automation is broken (hence the title, The Jetsons Fallacy).

Today's smart home solutions look more like universal remotes. The motion sensors, computer vision, and other sensor arrays create a system of false positives that need to be baby sat more than our old (analog) systems. This is a regression, and it will be many years before the tech is ready to move forward.

While I agree with the example you presented about dimming your lights when a movie starts, think about the use cases, and how horribly unpredictable we as humans are.

Instead I think home automation should focus on solvable problems that don't predict your behavior, but complement it.
I was idly wondering about "less" a month ago. https://news.ycombinator.com/item?id=8506813 It looks like my answer is "yeah, people are looking at that."
One of the (few) thing Google Fiber looks at when deciding to enter a new market is access. There's no reason to believe that Google would take a decade to cover the US if they could get the access issues sorted.

The more poignant question is, what will your neutral internet connection look like after a decade of full-blown monopoly? Title II is monopoly regulation, and there's no reason to believe the cost of Title II won't be formalised monopoly.
Try vue.js. Same general idea as angular, way less bs. However, the author did just get hired by meteor, so that is something to consider.
>> "I suspect internet access is what kills the joy of real work since you can be so easily distracted. Before you know it, one hour has passed and you didn't do anything."

I wonder if another part of the problem is that you can see other people's work online and give up when you see your achievements pale in comparison. I remember writing my first app - a web browser in VB - and when I did it I spent weeks working out how to copy and paste and create a menu bar etc. I even got joy from figuring out how to create a splash screen and create themes for my app. It was using a built in webview so there nothing very complicated about it but I had to read documentation and figure stuff out and it took quite a long time. I was very proud when it was finished. I can't imagine my feeling would be the same now. I could Google it, find the answer - ready to copy in to Visual Studio and run - and I would feel stupid for spending weeks on it. Then I would see someone who built a framework used by thousands of people on a weekend and I'd want to give up for good.
You'd make a good politician because you make a bad human now with all that word twisting.
This should do the trick (plus some heat tape): http://www.amazon.com/Farm-Innovators-TC-3-Thermostatically-...
It sounds to me like the value is coming more from management than the programmer. After all, you admit that few people have the skill to deliver that value and the programmer can't deliver it themselves.
Moonwatch Only: Ultimate Omega Speedmaster Guide and Perfect Christmas Present
> Too many side paths that amount to not much at all

Oh gee. Welcome to science. So many many paths in science lead to nothing. Often times years and years of research only to come up empty handed.
Most competent web devs can have something working relatively quickly -- even if it is an early prototype - like a week or two from a good developer. I would recommend hiring someone who already knows the stack you are using. Learning as you go, especially for the main devs, is highly problematic -- the chance they produce a pile of shit is very high.

Having a few junior devs around the experienced devs is okay, but only inexperienced devs (in the technology at hand) is a really bad situation.
For those you want to learn the functional programming I'd suggest to immedeately commence looking at Ocaml/Haskell instead to see the real big picture. Because it's of course adorable that you can write map and compose in JS (it's 2014, it can do it everywhere), but FP = many more serious things.
Surprised to see a rust post _not_ authored by steveklabnik
Here is a very good presentation of CO2 measurement values:

http://www.esrl.noaa.gov/gmd/ccgg/trends/

I'm still looking for a non-movie version that shows the whole curve we have (not just the direct measurements).

edit: forgot the link

Some more good writeups:
https://www.skepticalscience.com/argument.php
http://climatechange.procon.org/

If anyone has questions - I study this stuff.
Advocating two-column landscape format for scholarly online articles [pdf]
Message passing across threads is very easy with boost asio: you just post a callback to the respective io_service. That is effectively what Qt does anyway, but no Qt required.
Reportedly it's possible to achieve a similar effect on systemd by having too many journal files (on 208, but the distros backport patches into it constantly from the -stable branch, IIRC): https://bugzilla.redhat.com/show_bug.cgi?id=1112556
There's not a firm list, but certain commands should always be safe to run against hostile input.

If I type "make" on a project I downloaded, arbitrary stuff gets run. I accept that as part of make.

If I sha256sum a hostile file, that should never lead to RCE.
It's unfortunate that they chose to use un-semantic tags in all their examples. It's almost backwards. Other than that, it's extremely well documented and a pleasure to work with, and much easier to pick up than Bootstrap these days.
This is in an established corp (best practices, standards, workflows etc) - you could build things out of mud and they would still hold. Doesn't say much for/against this particular framework..
Start-up: Robinhood’s zero-fee stock trading service
Food production. Even today there are people without enough food. The planet isn't getting any bigger while the population grows each day.
If you don’t have the guaranteed endpoint integrity, the privacy of citizens (and everyone else) through encryption of communications is impossible.
I've never cared for a lawn in my life, so purely out of curiosity, why should a sprinkler system be on in the early morning? Wouldn't morning dew take care of watering grass around those hours?
I HATE web hosting affiliate sites, but this one is kinda cool
Article Series: Web APIs: From Start to Finish