skysight-inc/HackerNews huggingface dataset:
There are some really nice JS talks by Douglas Crockford on the now defunct YUI library YouTube page:
https://www.youtube.com/channel/UCTHcgWOTU6gPje1g_U29tfQ
Even though they are a few years old, they're still relevant
If you don't have an army, you don't have a "nation state". You have a clubhouse.
Perhaps there's more people in Paris that know how to make awesome croissants. Maybe it's considered "fancy" food in the US and marked up accordingly. There's a lot of economic levers to push.
IMHO, developer time is more expensive than CPU time; I don't want or need to have to write out all of those requires. That's the job of the autoloader. And if I'm writing my code remotely well enough, each section only uses the things that it needs. Granted, there may be some things that each request get that they don't need with the autoloader. But I can optimize later. "Make it work, make it right, make it fast"
To frame things in a UK context, which seems more similar to the Thailand situation then the USA.

The monarchy is (almost) completely separate from the political system. While many people might debate the pros and cons of the Conservatives versus Labour, UKIP or liberal democrats, very few question the role of Queen Elizabeth II.

In the UK, the monarch has the the right to veto legislation passed through the parliament but this right is rarely exercised. This is quite different to the US system where the president is ultimately in charge and has to fight for re-election every few years.

It sounds like the monarchy in Thailand has strived to maintain stability for the people in spite of an unstable political environment. This might explain why the people continue to believe in the monarchy in Thailand in a way which seems alien to anyone in the USA.
Then figure in the dwarf planets, asteroids, and comets, and we'll start to get to some big numbers.
Luck. Timing. Culture. Team. Etc. All have a greater impact than language. Anyone who says otherwise doesn't understand history.
The point being made is "I think a fetus is valuable." I get that. Duh. But even if everyone agreed, a fetus is still a different thing than a child. Believe it or not, there is hardly any disagreement about whether "abortion" of children should be legal.

Saying one thing while meaning another doesn't make the point, it obscures it.
"Why isn't my search engine an efficient file browser?"

Google isn't really a library; you can't just walk up and down the aisles until something pops out at you.

Which raises the question: What is the equivalent on the internet? If I want to browse random books until something pops out at me, where do I go on the internet?
Interestingly - this is a ban on their roots.

How much do you want to bet they're already working out how to supply new and renewing customers with certs provided by some other CA?

I notice the most recent StartSSL cert I got has a 3 year validity instead of their previous standard of 1 year - presumably in the hope that when my cert needs renewing they'll be able to provide that service. (I do have a handful of their certs which will expire during this 1 year ban. I'll certainly be needing to go elsewhere to renew them (finally time to learn how to auto-deploy LetEncrypt certs to Amazon ELB I guess, or maybe move all those domains to Route53 - I probably should have made time for that already...
Can someone point me to a live, public instance of Zulip that I can use to experience a real demo?
Ooh.

Mind, I agree with you, but given the Holy Documents Handed Down By Our Lord and Savior, Paul Graham, HN... might not be the safest place to say it.

Edit: so, I'm clearly getting a lot of downs on this... maybe sarcasm in reference to PG was going a bit too far. Oh well. I'm not deleting or editing any of it, because that's sort of dishonest.
I also liked Keith's previous version of this, given at Strangeloop a few years ago [0] and discussed here [1]

[0] https://www.infoq.com/presentations/php-history
[1] https://news.ycombinator.com/item?id=7054294
Oh I really do miss optional type hinting in.

Theres a lot of raise ArgumentError.new unless foo.kind_of? Bar

Going on in my code these days.
The way we detect planets only detect some of them.

The best method is to notice when a planet passes in front of its star, by how it gets slightly dimmer. That only works if its orbit happens to be directly between us and that star.
Wasting ingredients even a fairly small percentage of the time get's really expensive. This is one of those cases where a server with 90% up-time is easy, but 99.999% is really really hard.

What I don't think people get is it's no big deal to fail say 15% of the time at home. But, bakery margins are really tight and they can't afford that kind of failure regularly.
I've always found this idea intriguing and fun. It hasn't to be something in outer space, it can just be a landless state, constituted by people itself. Some opensource lessons about cooperation could be applied to create the foundational legal corpus. You would still be bound to your current law, but some conceptual political experimentation could be done bloodlessly as sometimes has happened in tangible nationalities. State sanctioned digital currency could rise some eyebrows.
I disagree. The reason that being born into an inner city black community is a devastating hand is precisely because of racism.

Race does not exist in a vacuum. Look at the legislation that makes possession a crime. Look at the way selective enforcement results in blacks being over represented in prison systems.

Look at the way the urban school districts are underfunded. You can pretend that the system is not racist, but when one racial group suffers disproportionately from legislation that is regressive, unfair and has not been repealed or changed since the era when Jim Crow was wakking, you have a racist system.

We can put feel good bandaids over some college admission laws and we can even elect a black president, but until we fundamentally rework the laws and institutions of this country, we cannot call racism dead. That is the opinion of someone who has not been pulled over for driving through the wrong neighbourhood.
Best comment so far.
PHP is wonderful as a thin layer of glue between your database and the web browser. It's when you write a thick middle layer that PHP gets unwieldy.

Business logic: Don't write it in PHP. Write it in PostgreSQL.

Authentication: Don't write it in PHP. Use Apache 2.4's mod_auth_form. Replace hundreds of lines of PHP code with a few lines of Apache config. When it gets to your PHP script, all that's left to do is read $_SERVER['REMOTE_USER'].

Authorization: Don't write it in PHP. Use one of Apache's modules (LDAP, DB, or even file) or if possible make your users all very restricted database users and use database permissions more.

Don't need a database? Then why not handle it all on client-side JavaScript?

I'll admit that my advice fits well with CRUD web apps. If you're doing something else, PHP may be gross.

But really, my goal in programming (don't always reach it) is for PHP to just make a simple database call and wrap the result in HTML. If you're doing 123 == '123foo', can you move that up into the database or down into the browser? If you're writing elaborate class hierarchies in PHP, I think you're doing too much in PHP. I write a few functions, if needed, but mostly move all data processing to the database or browser.
I don't believe for a second that this will fly (ha!) but possible answers are suggested by existing micro-states like Lichtenstein, San Marino and the Vatican: offer services which are appreciated by powerful and/or numerous constituencies in potentially hostile countries.
For a small-mid sized company with an overworked dev manager, hiring out flynn for the cost of a Jr Systems Administrator sounds pretty reasonable.
You can add a ReactPHP based HTTP server to your app to avoid reinitializing, but you'll have to deal with memory leaks between requests and process management yourself.
Due to lifetime elision, you rarely need to explicitly write lifetimes. I participated in the last Ludum Dare game competition, my game never used an explicit lifetime.

That said, it is true that Rust has tricky parts. The domain is inherently complex.
Very simple, the supply of people who want to be pastry chefs is increasing just as fast, thanks to the recent crazes (cup cakes, etc) and the explosion of reality tv cooking shows in the last decade that is making that career option a much more popular choice. I know someone who just quit their high-paying consulting job to fulfill her dream of becoming a pastry chef, and willing to take a considerable pay cut for it.
There are plenty of prices for excellence in young adult literature. The noble price shouldn't be one of them.
I think the point is, PHP won't kill you. It might be bad. But it is not in and of itself deadly.
If company is relatively new you can still help it steer into right technologies, so not always it is a deal breaker
> PHP is perhaps one of the easiest technologies to scale horizontally, because of its statelessness.

PHP is no more stateless than any other language out there. Statelessness is a design choice, not something PHP gives you for free. If your app write things on the local disk or use the default PHP session handler then it is not scalable by default. In order to write code that scales you need to make it scalable, it's not something automatic and certainly not special to PHP.
On WikiLeaks, Journalism, and Privacy: Reporting on Podesta Archive Is Easy Call
I'm noticing that they effectively used a series of rhetorical questions to try to make a point. The point is that the curve of worker skill to product cost doesn't have to be the same between a pastry chef and a software developer. That concept is more interesting to me than any references would likely be.
Tron 2.0 – Creating a Visual Language of Scale
Javascript actually has less problems than PHP. It also has proper lambdas, true lexical scope, and a shockingly good (if slightly confusing) OO system.

There's a reason that people claim (incorrectly, but still) that somewhere inside of Javascript there's a Scheme dialect, desparately trying to get out. This isn't true, but the proper lambdas and scoping are very scheme-esque.
It's a useful reminder that how ever far PHP has come, it still has a long way to go. Most of what's in that post still applies today, though a few things have been dealt with.
Returnly raises $3.2mm seed round for 'better online returns'
The subtraction isn't the issue, the cast is. the string "2016" is represented by the byte sequence [0x32, 0x30, 0x31, 0x36]. Casting this array to a uint32* in big endian gives you the integer 0x32303136 (or 842019126) while in little endian gives you the integer 0x36313032 (or 909193266).
> is there even a proper way to measure how good a language is?

Nope.

I mean.

They're all Turning Complete (except for the ones that deliberately aren't), and they're often good at expressing different types of problems.

So depends what you're trying to do.

Trouble is, it so often turns out you didn't really know what you were trying to do till you were nearly done doing it and then you're stuck with what you picked.

PHP is pretty good for building website prototypes, and can now handle the scale as they grow too really.

But "Good" depends on what you're trying to do, and what tools you already are running anyway.

Is there a way to measure how good a spanner is compared to a hammer?
It would happen if there's a big crunch.

Also, a lot of astronomy goes on the assumption that the laws of physics are the same far away as they are near by, and that they don't change over time. It's possible that if either of these two assumptions are incorrect that anything goes.

I'm also reminded of Arthur C. Clarke's famous dictum that, "when a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong."
I never said anything about your integrity but you inferred from my comment just like others will do from yours.

The difference is the individual you're disparaging is a real person with a reputation. You, like me, are a throw away account on a message board. You have no integrity because you have no identity.
It's the expected result for Google, yes; they do not support full pagination over their entire estimated result set. To get more results, you need to narrow your query.

(Did you only just find this out now? I'm finding it hard to take you seriously.)
I think it is worth reading that article in depth after scanning it quickly. It captures my own feelings about the state of the linux desktop very very well.
This blog is exactly what an SRE interview is like.

I breezed through these kinds of questions with the recruiter since I'm younger have a fairly fresh CS background.

Then, my first SRE staff interviewer primarily asked how I would build a data center on the moon. I work on the FreeBSD kernel and TCP full time. I know what BDP, window sizing, head of line blocking, etc are way beyond what a typical SRE would and how communication latency would cause major issues. That confused the questioner. I can't think of anything else I'd have said wrong, my background is systems engineering and I know more about power distribution, HVAC, and data center design than I care to. The lady was skeptical of my answers and it felt really humiliating even though I would rate myself more knowledgeable than my questioner, because of the candidate/interviewer positioning and failure.

The next man, on another day, asked me a bunch of math trivia like estimating the angles on the hands of a clock and orders of magnitude guesses of a small item like a marble to fill a room. I told him I was no longer interested in working for Google and he was really startled because "he didn't get to ask me systems questions yet".. well, good luck with that.

Everyone was really sad at that point, including the recruiter. Nobody from Google has contacted me again, which is a relief. I found the entire process gross.
Yeah, the rate of multi zone failures is concerning. Was planning on moving our primary API behind the GCP load balancer but will have to reevaluate that.
At least it's not hosted on youtube.
This article is best read with Crystal Method's "The Grid" from "TRON: Legacy Reconfigured" pumping in the background...
> [Gödel] believed in ghosts; he had a morbid dread of being poisoned by refrigerator gases

I wonder how this relates to the refrigerator design Einstein worked on, "motivated by contemporary newspaper reports of a Berlin family who had been killed when a seal in their refrigerator failed and leaked toxic fumes into their home":

https://en.m.wikipedia.org/wiki/Einstein_refrigerator#Histor...
Guess you can say Crystal is a totally different language as well. It's just to me, Crystal still has the same feel as ruby and Cython doesn't. Again, it's just my opinion, I won't argue if you feel otherwise.
A neat followup might be to take the job-search data and then put together a list of which technologies have the highest developer interest. This could be quite useful for companies or projects trying to decide on a tech-stack or tooling.

Even better would be to compare supply vs. demand and come up with a ranking of tech combinations that people want to work with but few companies are using. For example, Rust + Postgres gives one result that's actually hiring. That one company could conceivably get quite a boost to their hiring efforts if there are many developers that want to work with Rust + Postgres, and other companies that pick that tech company would also get a similar boost until it gets oversaturated.
I assume they fail to grasp their ineptitude. Frequently doing a good job is not enough. In a professional setting failure has real costs and you are directly paid to minimize those failures.
amazon arguably isn't really fair comparison for < $1 items because amazon doesn't really sell anything for less than $6 anymore because (I assume) they don't want to lose money on prime shipping if that's the only item in the shipment. OTOH I don't know what a better comparison would be. ebay would probably just be a similar vendor shipping from china.
Do you really find it hard to believe that a more experienced pastry chef can make better pastries? I think this is the same frustrating myopia that makes people assume they all could easily write software the way you do except in reverse.
An anecdote against: I've been making beef fried rice for a little over a decade (but probably less than 500 times total). The best I could do in the first year was probably nearly as good as the best I could do five years in, and five years in was easily as good as any I could do now. It's a very simple dish, but then, that's the argument about these pastries as well.
Sirajology https://www.youtube.com/channel/UCWN3xxRkmTPmbKwht9FuE5A

Covers machine learning related topics in a very fun way.
Ask Chipotle if that matters.
Okay, so you're saying that:

(0) Bash is strongly typed. Everything is a string, so there can't possibly be any type conversions, implicit or explicit.

(1) Any language with subtypes is weakly typed. For example, Haskell with Rank2Types or above: every lens is a traversal in a canonical way, and indeed the type checker lets you supply a lens in a context where a traversal is expected.

(2) Rust is even more weakly typed: boxes (as well as other user-defined pointer types) are implicitly converted to references, iterable objects are implicitly converted to iterators, etc.

There's no precise technical definition of "strongly typed", but AFAICT, the intuitive idea is that a "strongly typed" language prevents you, or at least makes it difficult to do things that aren't likely to make sense, like treating the same datum as a number and as a string in different places. This is independent of whether the language has implicit conversions.
Not having to worry about upgrades. Major upgrades cost time, energy, and effort. I don't want to expend energy on it. I don't think playing sysadmin is a good use of my time.
There's also $data->key->value[0], which is the default. But yes, dots are shorter.
From a thread about the data breach:

> Investors are conflicted: on the one hand, Yahoo had a data breach that will cost them trust, but on the other hand, investors are surprised to hear there are still 500 million Yahoo users.

https://news.ycombinator.com/item?id=12559594
Can you give a specific example where you think you need dynamic types? The diff operation you described sounds like it could be made generic pretty easily, but I may be misunderstanding the goal.
I don't think so. You either keep state between requests and therefore get problems like memory leaks (which often happen in large Ruby or NodeJS apps written by not very experienced developers) or you keep no state and have to do initialization on every request.
These books are more for casual reading, except for Book 3. If I may, do you have more recommendations similar to Book 3? In addition to my personal interest, my read of the OP request was he looking for more technical details. For myself, what books are good for a second or third course in stats? I have a finance background, so I'm familiar with the intro stuff in Book 3.

As a recommendation to the OP, "Collective Intelligence" by Toby Segaran is amazing.
RE:DOM's new look is on FIRE
All strings in C# are UTF-16.

However, it exposes the encoding directly as a sequence of 16-bit ints. In other words, if you iterate over a string or index it, you're getting those, and not codepoints (i.e. it doesn't account for surrogate pairs).

Note that this only applies to iteration and indexing. All string functions do understand surrogates properly.

On the other hand, C# (or rather .NET) has a way to iterate over text elements in a string. This is one level higher than code points, in that it folds combining characters:
https://msdn.microsoft.com/en-us/library/system.globalizatio...
> (see the tully monster for example).

Wow, that looks like something straight out of Spore! [1] Thanks for mentioning this! Weird creatures like these on our own planet only pique the excitement for seeing how truly alien life on other planets must be like.

[1] https://upload.wikimedia.org/wikipedia/commons/6/67/Tullimon...
Well, perhaps, but at least Google had been taken to court for hiring collusion.
That's really the question. Is language choice a signal for other properties of the culture? And if so, which of those cause success?
Without any support there's no way to evaluate it, interesting or not.
I like this size comparison:

https://upload.wikimedia.org/wikipedia/commons/4/42/JWST-HST...
This past weekend I was at Desert Trip in California, and I got the chance to talk to neighbors from Austral-Asia, Europe, and the US. This was a diverse group to say the least, ad we were all camping next to another on 408th and Broadway. The conversation got onto VR, and we all agreed, without a doubt that their is no substitute for human contact and that the whole term Virtual Reality was a contradiction and a not very slick marketing term. No one wanted anything to do with VR. In fact, the conversation about VR was so disgusting to all of us, we all had to just drop it. NO ONE wanted VR, and any company betting on it is betting against the house and the players at the same time. We all thought the big bets could be used for much better causes. Just some info.
I can imagine an expensive chef to setup processes that allows cheaper personnel to keep producing quality party. Slowly that process will suffer from time rot (eg: different floor that requires a diff cooking, but cheaper labour can't figure it out), also innovation will suffer.

I see the exact same thing in dev envs, and even more so in ops/sysadmin. Cheaper unskilled labour going through old fashion processes without questioning and never trying to improve.
I would go one step further and say that there is no meaningful default for these things. It all depends on the context, and there's no single context that is so common that it's the only one that most people ever see. Thus, it should always be explicit, and an attempt to enumerate or index a string directly should not be allowed - you should always have to spell out if it's the underlying encoding units, or code points, or text elements, or something else.
There are plenty of great server-side languages and environments. C#,Java,Scala,Python,Ruby,Haskell.

If this was about JavaScript and Front-End I might've agreed with you (there are transpilers but interoperability with JS modules can be tricky), however in the realm of servers there's so much freedom.. so why choose PHP out of them all?
Yeah, Yahoo was already dying of attrition anyway. I suspect the majority of those accounts were not active.
I never said it was for a beginner, just that it was well designed. Lifetimes are no more complicated than stuff you regularly run into in C++, though.

Python is a great beginner-friendly language, but that doesn't mean it's well-designed in other respects or appropriate for large software projects.

It wouldn't really make sense for Haskell to "support OOP" in the usual since. The OOP paradigm is mostly useful when you have mutability. Another way of looking at it is that you don't need OOP in Haskell because it exposes better ways of interacting with data that aren't present in most OO languages, like ADTs and Typeclasses.
I wouldn't call an account almost three years old a "throwaway" anymore.
There's always openssl s_client
Unless you are using ReactPHP, PHP doesn't handle Http requests in any serious production configuration, the server fronting PHP does( Apache ,Nginx). But PHP wasn't design with Async programming in mind so using ReactPHP is more than tricky since most operations are blocking.