skysight-inc/HackerNews huggingface dataset:
They are currently being used in Africa and South America primarily for industry use (telecommunications mostly).

No, you won't run an aluminium smelter with them, but for load balancing during those (pretty rare!) times when you don't have either solar or wind they are fine.

I don't know about the temperature problem. I know they are used here in Australia at 40C+ and in Africa in similar climates.

I think that they are actually better for industrial use than home use. They aren't silent, and they need to be cycled. The noise isn't an issue in industry, and in home use I know the power cycling can sometimes be a problem because it is hard to find somewhere to dump the power (currently the solution is to dump it to heat, which isn't great - or alert the homeowner and get them to run a pool pump or something).

RedFlow (one manufacture) is in the same building as me, and they have an interesting report: http://redflow.com/wp-content/uploads/2015/06/Diesel-Runtime...
One thing I didn't see in the article: in addition to cache misses, the list stores 3 words per word; the array between 1 and 2 (up to 3 only when reallocating,) so array touches less RAM, even when inserting.
Read the comments written by those you respect. Those you aspire to be!
> pay close attention to those negative emotions, because they're usually trying to tell you something

No. They're always trying to tell you something. That's all emotions are. And they've already spoken, so arguing with them is futile. They're telling your brain how you feel so you can act intelligently on them, not so you can turn around and argue with yourself in the mirror.

There are no negative emotions. They're dumb and honest. There is no "how you should feel". Your brain is the only organ smart enough to pretend. You feel a certain way because that's the way it is. We should always start there.
You abstractly argue that bad things follow from bad things. Whether that concretely applies in this specific instance or not is only implied. Of course that leaves a lot of room for interpretation.

Whether the laws in question are just or whether the culprits in Cyprus will be brought to their punishment in prison is open. That's what I mean, you didn't understand.

I gave my only argument, trying to mediate between the two opinions, trying to consolidate them. I hoped that was obvious. I am also torn between these two extremes, and avoided to build a line of arguments.
I've seen rankings drops following drops in crawl rate.
May I suggest NATS Queuing as an alternative. [1]

[1] http://nats.io/documentation/tutorials/nats-queueing/
> The wrapper to fit Lambda into a client-server synchronous-invocation world is API Gateway.

So yes, there is a server indeed. Why call it "serverless" then ? because one part of the stack uses pubsub ? then call that part a worker queue because that's what it is.
Any specific tool for making the architecture frames [0] ?

[0] https://raw.githubusercontent.com/ustwo/ustwo.com-frontend/m...
Seems there are many variants of this type of tech. PBS [1 - video] had once called AGRUS [2 - wiki] (looks older 2013 and more advanced). They also deployed something like this in Rio for the Olympics [3 - blog/video].

[1] https://www.youtube.com/watch?v=13BahrdkMU8

[2] https://en.wikipedia.org/wiki/ARGUS-IS

[3] http://www.sporttechie.com/2016/08/01/surveillance-blimps-to...
Our emotions don't tell us shit. They are straight-up wrong, half the time.

Our biological OS is not constructed for the current world. That is why, even when everything is going right, we have intermittent moments of anxiety and depression.

This is chronic. The moment you ignore our biases, you fall into some deep shit.

And you can never get out; you can't see your own biases.
Taxes can be progressive, flat, or regressive. This is actually one of the most important qualities of a tax.

A carbon tax is decidedly not progressive. Take a look at the carbon map [1] of the 'Americans Carbon Footprint' and you will see, the problem is not the rich motoring around in their their yachts.

Now, the biggest factor in carbon footprint is the zip code you live in -- due mainly to energy use and transportation costs. So does a carbon tax vary based on the zip code of your primary residence? Seems absurd to me. So we have to start by admitting that any carbon tax we do come up with may not actually tax a large part of your carbon emissions. Which is to say, it likely would unfairly target certain products based on their carbon footprint while giving a free pass to others. While taxing some carbon might seem better than taxing no carbon, IMO a tilted carbon tax is worse than no carbon tax.

A gasoline tax approximates transport carbon footprint. It also makes electric and public transit more desirable. You can certainly also tax electric/natural gas/oil based on their footprints. This would be effective, but again, regressive.

If you take out the part where people are paying for their carbon footprint and go back to just taxing the rich, it's not really a carbon tax anymore.

It's not like people can report their carbon footprint on their 1040. The only way to tax carbon is to tax purchases at sale -- let's call it a CAT - Carbon Added Tax. Such a 'CAT' would be regressive.

Generally, if you subsidize purchases which lead to lower carbon footprints, the rich will spend more money on those qualifying items. For example, solar subsidies. This is an example of a non-regressive approach to encouraging carbon shrinkage through the tax code. SolarCity calculated that lifetime net carbon savings of the typical solar install was 150 metric tons.

[1] - http://shrinkthatfootprint.com/american-carbon-footprint
A majority of the websites that blekko, a google competitor, contacted to ask for robots.txt access ignored us.
I can wake up 7:50 and be in work, showered, by 8:10, including the 5-10 min commute. I think it varies a lot by person, just like productivity through the day!
Whatever. If I go to bed early, I roll in my bed for 2, then 4, then 6 hours and not find any sleep. And that's on a good day. On a bad one, it will be for 8 hours and then it's time to wake up.

When I was a kid, my folks put me in bed every evening at 8 PM, sharing the same false assumption as you. And I spent hours after hours watching the darkness. I would almost always fall asleep later than them, and often not until 2 or 3 AM, sometimes 4 AM.

When I was in middle-school and high-school, it was terrible because there was no mid-week day off as there was in primary school, and because it started earlier (and there was a bit of extra commuting). As a result, since I wouldn't fall asleep before 2 AM on any day, I was actually sleeping as much during the 2 days of the week-end as I was sleeping during the whole rest of the week (5 days).

In high school, I experienced a week there or there when I was totally er... off, in a mist, because of exhaustion. But even that didn't make me able to sleep early. The next year I was so exhausted that I fell asleep at noon one day and woke up 3 days later in the evening.

Then I was in University or Engineering school and those were the good years because attending the lessons was not mandatory and there was nobody to tell me to go to my bed or my room early in the evening.

30 or 40 years later, I am typing this message, it is 5:45 AM and I might fall asleep soon.
Nasa/openmct: A web based mission control framework
De-partitioned Housing
Thank you! We are still figuring so many things out, but we want to be as transparent as possible if it might help others learn about co-op startups and different ways of doing things.

The hardest moments have probably been at structural transition points. We used to have a much more open "swarm" approach, with lots of volunteers and part time contributors. It was great for bootstrapping the project off the ground, but we reached a point where we had to hire a core team for long-term commitment, and get a lot more focused. The result was some people leaving. It was challenging, but we navigated it through very honest and open communication, and all making decisions with the good of the co-op and social mission above our own individual preferences. This handbook page talks a bit about our organisational structure history over time: http://loomio.coop/working_together.html

What would I do differently... in some ways I think we were slow to learn certain things and we could have moved faster. We are a very diverse team, with backgrounds in social change, facilitation, community sector, and civil society, as well as business, technology, and startups. It was a long process to integrate all these perspectives into one coherent product and business model. But I also think that diversity, and going through that process, makes us much stronger today. Now we're pretty good at thinking strategically together and getting the whole team very focused. Working in highly collaborative and inclusive ways often means investing more time getting everyone on the same page, but the benefit is once you get there you can move together very effectively.
I would ask what exercise was tried, how regularly it was performed, and how long the effort to exercise was maintained.

Not saying that exercise is always the answer, but different people respond differently to different types of exercise. Consistency and regularity are also important.
Don't forget that TPP is also about doing an end-run around our own Congress. Once something is locked into the agreement it becomes near impossible to change it unilaterally.
Been down in the deep depression pit of darkness myself. Your career isn't worth losing your life.

There's lots of good advice in these comments. Don't make any final decisions in your current state of mind. Seriously. Seek help out of the darkness. Finding a therapist who is a good fit may take some doing.

For some great perspectives:

http://www.stevepavlina.com/

http://theancientwisdomproject.com/
Even with only 25% growth per realloc, you hit logarithmic overhead (only with a higher k because more actual copying.)
I'm responsible for the Objective-C part, so please let me know of anything we can improve there. We have a couple of tutorials at http://www.grpc.io/docs/tutorials/ and a quick-start guide at http://www.grpc.io/docs/quickstart/objective-c.html . For bugs and connectivity problems, filing a GitHub issue would be super appreciated.

If you look at the example code, you'll see that RPCs aren't modeled exactly as local function calls. You're right that that wouldn't work very well. The libraries for all or most languages let you make RPCs asynchronously, without blocking the thread. And all of them provide with ways to write and read RPC metadata (headers and trailers).
Earnings reports are the worst. Most of the economic numbers and other statistics are released in a machine readable format by a few companies that compete on speed. (There are some anomalies that come over the web and they are horrible to deal with.)

Earnings reports though I've tried numerous things from subscribing to services that release numbers electrically to writing parsers based on prior reports. Earnings though you care about things like one time charges, gaap and non-gaap numbers, etc. They are one of the less consistent things to trade.
Would you want to work for a company that has this policy? I certainly wouldn't.
So what if it's India? I bet you wish it was in SV asshole...
yeah. I did this when I worked for myself, but I found that with the addition of social (and business social, and errands that must be done at a certain time) I would end up either missing appointments or waking up mid-sleep cycle.

I mean, the regular down 10 up 14 isn't great for me, either, I seem to be on a 26 or 28 hour cycle naturally, but I end up getting a lot more uninterrupted sleep if I keep it to a mostly 24 hour cycle that very slowly creeps forward, with occasional resets. (and end up being a lot more productive when awake.)
Not quite sure. Maybe look for different ways to break out of your depression? Usually I find that I'm ignoring really important areas in my life, and just squashing it under my anxiety. For me, the biggest ones are exercise, and relationships. Once those things are dialed in, things usually start to run smooth again.

For me, exercise is one of things that's actually in my control, and the return-on-investment can't really be overstated for how well it's worked out for me. It helped me get outta lot of ruts, and get over some deep internal issues I was grappling with. I know it sounds dubious and unscientific, but it's worked for me and I think intellectual folk tend to write this off for whatever reason.
I think we might be thinking about Serverless slightly differently. To me serverless is not just AWS Lambda. It's a broader theme that encompasses Function-as-a-Service technologies like Lambda and Backend-as-a-Service technologies like Firebase & Auth0.

Combining FaaS, BaaS, and using certain techniques and patterns is what makes Serverless. As a developer I am plenty aware that there are servers - I don't feel that there is any voodoo or black magic. However, when someone says that they have a serverless system I immediately understand what they are trying to say. They are saying that they don't need to manage, provision, scale, and look after servers. Honestly, the world "serverless" is a lot less confusing than "cloud".

I am not sure what you mean by "there is still a server fronting the whole thing". You don't need to scale the API Gateway yourself (again it's a managed service). Same goes for Azure functions, Google Cloud Functions and OpenWhisk as they all have HTTP listeners built in.

I understand where your thinking is coming from. There was this article that tried to address it: https://serverless.zone/serverless-is-just-a-name-we-could-h...

Edit: fixed sentence structure.
> I don't have the option to stop working for a while. I have the savings for it, but it's unacceptable to my wife.

Don't stop working - if you're not careful it can exacerbate depression and you'll find out in 1 year that you're still just as depressed but now you don't have any savings either.

Find a better job. It doesn't have to be Big-4, but you need to be doing something productive with your time.
Getting Down to the Wire. Applications for Retail Innovation Pitch Event Due 9/1
> Damn. That's terrible. We are never going to get anywhere with 20 executions a second

...

> Lucky for us there is a trick we can use to greatly improve that speed.

I just dusted off my fuzzpy project [1] this week and was bringing it up to date with recent CPython, LLVM/libFuzzer.

> Notice the speed: 373.4/sec, up from 20! And we've already found 100 unique crashes!

Most of my test cases run at < 10/sec. I feel like I just got lapped while I thought I was on a casual solo stroll. O.o

I intentionally left Py_InitializeEx() in the critical section for fear of contaminating global state, though. But I see that I should've at least experimented with it out.

[1] https://bitbucket.org/ebadf/fuzzpy

EDIT: sorry, I went a little off the deep end -- this post is in response to the article listed in the first paragraph "After finding 1800+ crashes in Python 3.5 using a method shown here ... "
Our biological OS is not built for dealing with time.

1. We suck with memory. We re-write memory every time we recall.

2. We suck with delayed gratification. No other animal had to invest. We haven't evolved past that.

3. We suck with time estimates. The engineering trope of "3x the amount of time you think the project would take" illustrates this point. There is something in Pragmatic Programmer, too.

That is why we need calendars, planners, and timers. People who rely on their conception of time are ignoring the limits of their underlying OS.
You can also get QuickCheck for Erlang, although that stays at the Erlang fuzzing level, not AFL style branch fuzzing. Still, finds bugs!
Yup, this is exactly what happens. Basically the same as the "make whoever is in front of you happy until the big boss puts his foot down" anti-management pattern. It can work for periods if the big boss knows what hes doing and respects the employees, but otherwise, destined for disaster.
hotstar.com broadcasted Olympics free of cost in India. They aren't public funded.
Why does a bigger span of ice make it more resistant to temperature changes?
While I think that JS's loose typing is a little annoying and certainly isn't what I'd build if I were designing the language from scratch, it just isn't much of a problem for me in practice. Type errors in general (either of the implicit coercion variety or the dynamic typing variety) aren't much of a problem. They rarely happen, and when they do, they usually take all of 5 minutes to track down and fix.

I find that the big benefit of types are in documentation. They are executable, explicit, compiler-checked documentation of the programmer's intended usage. Without this, it becomes much harder to read through and comprehend a large codebase that was mostly written by other people. It becomes even harder to change it.

I like Python, I like Javascript - but they have their uses, and those uses don't include large-scale mature software engineering. I actually argued otherwise for my first couple years at Google (where both are used extensively, though the JS is largely statically typed), but eventually saw the wisdom of more experienced engineers in this, and relegated my Python to exploratory coding.
[video]Grandmaster Flash Talks “The Theory” of Being a HipHop DJ
Remember that since our general purpose computers are approximately Turing Machines, they can simulate anything, including better general purpose computers.

An OS is just a simulation of a "nicer" computer than the one that is natively exposed by the "real" one (i.e. the hardware).

Normally, "nicer" is pretty subjective, but in the case of computing it almost always means only two things:

* We simulate many more computers than we actually have (i.e. timesharing and multitasking)

* We simulate computers that are much easier to program.

In other words, an OS is just a simulation of having access to a bunch of nicer-to-program computers.

But, this ends up implying a multitude of features:

* Simulating many computers requires having a scheduler and process isolation. If we decide that we want individual users to have privileged access to their simulated computers, then we end up adding security features related to authorization and authentication. If we decide that the simulated computers should be able to communicate with each other, then we end up with networking since there is little difference between two simulated computers running on the same box, and two simulated computers that are running on different boxes.

* Simulating easier-to-program computers requires having memory management, virtual memory, I/O abstraction, graphics, portability, etc.

Since we end up with most, if not all, of the features that most people think are requisite for an OS, I think that my definition is minimal.
In hindsight, I am now convinced this plan was fundamentally flawed. The market for paid productivity apps for iOS is simply too difficult.

When even a stalwart Apple partisan like Gruber will concede this you know things have gone horribly wrong in the iOS app market. The bulk of the blame here lies with Apple and their stewardship of the app store. They can push the iPad as real productivity device all they want but until they do something to make selling anything but games on the appstore worthwhile they're wasting their time.
This is the boilerplate I used last time: http://extensionizr.com
Animation That Explains Multi-GPU Algorithms [video]
How do firing decisions get made? If workers own a part, I assume they can still be forced out. Does it require a majority vote though, or do one or more people have that authority granted to them?
There is a lot of price pressure on iOS apps, people expect them to be free or at least under $2. At that price you need to sell a lot of apps to make a profit, and probably very few apps reach that level. I've tried the opposite, selling a higher priced app and accepting the much lower sales numbers, and I think it has resulted in a better return than going low cost, but it's still not earning enough to grow. I do look at the prices that desktop apps get with envy, so maybe it is time to go back to that market? The idea about designing for mobile first though, that makes a lot of sense.

John mentions having to redesign for iOS 7, but the reality that there are many of these events that mean that you have to keep developing. New iOS versions, new screen sizes, WatchOS, (tvOS), new input methods, updating UI, all add up to quite a bit of work just to stand still feature wise.

I think the days of making money on the App Store are gone.
The Ultimate List of 300+ Slack Communities
It's going to depend on the state. Try to find an organization similar to this in your state that you can talk with.
When I pull it up, your profile looks blank.
Size of NYC's MTA
Ever tried to write a web scraper that works on every website on the internet?
Interesting, I am on Chrome. Perhaps it was an omission and they fixed it...
> Undergrads are often assigned boring research jobs and are paid less.

I agree paid less, but disagree about "boring" research jobs. It probably depends on your school and your major. Nuclear Engineering at NC State got me to research molecular dynamics GPU techniques (this was around 2010) to simulate rare events (such as radiation-resistant material interactions) in order to get real-world simulation times to the order of milliseconds, which is a whopping 1000x speedup from the usual microseconds. I got access to the school's supercomputers just like any other physics grad.

My work later moved to the CASL (Consortium for Advanced Simulation of LWRs[0]) umbrella, and I was not the only one. None of the topics were boring, and the general impression I got from the department head was that undergrads were as capable but just requiring slightly more guidance.

It was a great funnel for getting undergrads to continue their research to grad school and ultimately to a PhD. I did not continue, but still have several friends that are pursuing their PhDs.

[0] http://www.casl.gov/
1) I am reluctant to stop taking it. I am accustomed to the initial effects -- a missed dose here or there isn't noticeable, but I don't want to lapse into fatigue from abstaining or miss out on the benefits of sustained intake. There may not even be a benefit to long term supplementation so this concern is a bit unsubstantiated.

2) I didn't track or log differences in my exercise routines so I can't quantify anything. Qualitatively, its easier to exercise consecutively and I have been able to increase magnitude on my lifts by ~20% across the board. This could be attributed to shorter recovery time and reaping the benefits of adding volume to training. The strength gains plateaued 6 months in. I am in my 8th month of taking basis.
Sitting Up: A brief history of chairs
JasperReports Server 6.3.0 Support and Enhanced Compatibility Mode in Word 2013
The long awaited version of Aspose.Words for JasperReports 2.8.0 has been released. This release also includes support for JasperReports Server 6.3.0 and bug fixes to the Aspose.Words for JasperReports product. This release also includes some important enhancements, such as compatibility Mode in Word 2010/2013, background band (table) does not exported correctly in output Docx and LastPageFooter band does not export as Word document’s footer. Aspose.Words for JasperReports makes it possible exporting reports from JasperReports and JasperServer to Microsoft Word document (DOC), Office Open XML (OOXML, DOCX), Web page (HTML) and plain text (TXT) formats. It is written purely in Java and is provided as a single JAR file that can easily be deployed on the machines running JasperReports or JasperServer. Aspose.Words for JasperReports exports flow layout documents that are easy to further edit in Microsoft Word, if necessary.
BrightWork's JavaScript SDK – build your back end faster