skysight-inc/HackerNews huggingface dataset:
That's a fair perspective, but that doesn't ring true for me.

I've spent money on Spotify, Prime, Patreon (to support local podcasters and niche YouTube content), Twitch streamers, software (Sketch, Lightroom), Marvel/Invision... all because I got to sample the software or produced content and want to support the artist/developers.

Anyways, good luck. Competition and subsequent innovation is always a good thing.
I've lived in Austin my whole life, started working in tech 20 years ago.

I could count on 1 hand the number of female developers I've worked with.
The majority of my comment was talking about Matrix, which is an open protocol with free software server/client implementations.
Not the above commenter, but Google Earth VR is like something out of a sci-fi film from 20 years ago. I was sincerely impressed and enthralled. Of course, the more street views they can capture, the better it will get.

There are other education experiences like BBC Home which is one of my favourites. Another, Mission:ISS allows you to explore the ISS and control the Canadarm to dock a module. Highly recommend them.

https://www.oculus.com/experiences/rift/1246744618768922/

https://www.oculus.com/experiences/rift/1178419975552187/

edit: I almost forgot, Go For Launch:Mercury is also very worth it. You can choose manual mode which puts you in charge of setting the launch procedures. The graphics aren't as good as I'd like, but the experience is good.

https://www.oculus.com/experiences/rift/752373261529153/

---

As a platform I really think it's capable of more than it's really doing right now.

I wish there was a way to open it right up for the more adventurous instead of relying on sometimes-working-sometimes-not tools like VorpX.
A lot of people on this thread are conflating Bitcoin and other cryptocurrencies for what the SEC is talking about in this statement: tokens that are acting as securities. They do not mean Bitcoin and similar tokens (ETH, LTC, ADA, NEO, etc). If you've been following the SEC's other statements, testimonies, and senate committee hearings, you would know that they do not have a problem with digital currencies per se. That is outside of their mandate (those fall under the CFTC's purview). What the SEC is concerned with is companies that issue digital tokens which act as securities. That is to say, the reason people buy the tokens is the expectation that the work of the company that issued the tokens will cause the value of the tokens to increase, and that is the motivation for people to buy them.

This differs from Bitcoin, which is not issued by any company and has no central organization that does any work or promotion of the token.

The response from American cryptocurrency exchange Bitfinex expresses the distinction between securities and other types of tokens:

“As a U.S.-based digital currency exchange, Bittrex is committed to incubating new blockchain technology projects and offering innovative, compliant digital tokens to our customers. Bittrex uses a robust digital token review process to ensure the tokens listed on the exchange are compliant with U.S. law and are not considered securities. Bittrex is committed to helping advance the United States’ global leadership in this emerging industry, and we look forward to continuing our proactive dialogue with the SEC and other regulators on how to build a secure, fully-regulated environment for blockchain that encourages innovation and economic growth.”

https://support.bittrex.com/hc/en-us/articles/360001525152-B...

They seem to be prepared to meet the SEC in court to argue that the assets they facilitate trading for are not securities.
Having used graphql in production environments for about 6 months now, I would say that it is amazing and should be a first option for new APIs. The big selling points for me are:

1) self-documenting and explorable API (via GraphiQL interface) mean I don't have to ask backend if this or that value has been put in there.

2) expensive-to-fetch attributes returned in a query are only fetched/calculated if asked for. This means we don't need to split off logically similar queries into two REST endpoints to optimize the site

3) strict type and value checking mean I will always get back what I expect to get back. Attributes can be deprecated and throw a warning if I ask for them. If I ask for an attribute that is outside the spec it will give me an error. This is great for code maintainability.

4) frontend and backend can communicate more effectively with a standard contract. Building a react frontend with Apollo made me constantly question why I was getting paid so much to do what I did, it was that easy.

5) Implementation specific, but Apollo is really amazing and handles caching, dependent queries (I can ask a set of queries to refetch if I perform an update), and is dead simple to create a frontend around.
Back in the early days (2011) Paypal prevented me from buying Bitcoin. At this point, I was out of options to purchase any, and obviously, this emboldened me to buy more as the requirement was clear.
Wire them into a networked cellular service, and condition them to depend on remote control buttons, that track them everywhere they go, as early as possible.
I use and like Postgres, but it's crazy to say there's never a scenario where putting data somewhere else makes sense. You just named two examples, Redis and Elasticsearch.

It might be fair to say something like: if you have a general purpose OLTP workload with lots of individual reads and writes, with lots of interconnected relationships between models, where you'll need to query and index by lots of different attributes, then you'll probably see as good or better performance with Postgres vs a NoSQL alternative.

But there are other uses where you'll have a much easier time using a message queue, a streaming platform like Kafka, flat files in S3, some ingestion system to feed HDFS or Redshift, a sharded key/value store like DynamoDB, etc.

I would even go as far as to say, in my own anecdotal experience, for every case where I've seen an app struggling because they're pushing a NoSQL DB beyond its sweet spot, I've seen another app struggling due to pushing Postgres or MySQL. Things like writing all application logs to the primary Postgres DB, or using it as a message queue. To be fair, the catalyst of the problem in these cases is usually the mixed workloads in a single DB instance, and a separate instance of Postgres would work better. But still, other tools that are built for a much more specific purpose can go even further. Plus they can be easier to tune, with Postgres you'll often have to worry about configuration and things like query planner statistics, vacuuming, and XID wraparound.
> Bitcoin doesn't have any men with guns to set a baseline demand.

I think that depends on where you're spending it.
My Nexus 5x cost me $250, lasted 2 years, expect this $150 Moto x4 to do the same. iPhone is $600+, I could still get another phone!
और क्या हाल है भाई? If you're using an Apple device, you could try using a transliteration keyboard. Type in English, the word is printed in Hindi (I dunno if they have a transliteration keyboard for Bengali)
Steam VR/Vive has "AAA" non-exclusive titles.
These kind of things are fun to think about and tricky to solve. My thermostat in my hallway for example, if I set to 69, will turn off but it still feels cold. I used an IR thermometer to see that it is 69 right at the height of the thermostat, but is a gradient down to the floor where it is like 65. So there are thermal layers in the house. I started to put a small fan on the floor blowing up at the thermostat that will both mix the layers and blow the cold floor temp up at the thermostat. It will kick on and after a bit the whole house will be uniformly toasty :) I started to think why this kind of thing was not built in, but it would require air inlets and outlets at ground level and ceiling level and two thermometers, so it starts to sound too complicated and expensive. I see why people like in-floor heating now.
My experience trying to build out the server side backend in GraphQL for various features was miserable:

* you are adding an additional abstraction layer on top of your data store (in our case, SQL), with significant cost in complexity and speed. This was for queries that served many thousands (or more) of requests a day, btw, so maybe it would be fine for apps w/ just tens or hundreds of users.

* trying to get any complex queries performant was _very_ difficult. We knew how to avoid n+1's w/ SQL and our ORM, but doing so with GraphQL loaders was very difficult and required some very intense promise-based code that was incredibly hard to debug or understand.

* the abstractions felt all wrong - it often felt like our the GraphQL loading layer was completely disjoint from the existing domain model. Building out the GraphQL layer often came at the expense of the domain layer -- maybe this was due to our own inexperience in mixing the two ? Anyway, it felt similar to how impossible it felt to build a decent domain model back in the days of Javabean / EJB frameworks.

That was my experience around a year or year and a half ago, anyways. I definitely see the value in the declarative nature of GraphQL for client usage, but the cost on the server side felt _very high_ to make it a reality.
https://wire.com/
This, and many incidents like it, makes me think that running tests 1/10/100 years in the future should be a standard feature of test runners and CI systems. (on by default)
Matrix has native clients[1], as well as a weechat plugin.

[1]: https://matrix.org/docs/projects/client/quaternion.html
So do I understand you correctly that you’re categorically excluding any kind of experimental evidence, no matter how well controlled or rigorous? That, so long as there is no breach of the source of the technique, you can’t be convinced?

I understand that any one person’s anecdotes are weak evidence, but your comments are going much further and claiming that such tests can never be evidence, even though much scientific knowledge is similarly obtained.
Sounds like Hillary Clinton
I am a 31 year old man, drinking in a bar, alone, weeping as I read this story. My heart goes out to you and your family. I’m so sorry.
I've pointed out this consequence of "put TLS on everything" before, but people shrugged it off.
Sunrising Bedding Good Sleep Doesn’t Have to Be Expensive
As we all know, the internet is about the free and open sharing of other people's ideas !
This is my favorite thing I've seen on Hacker News in weeks: immediately made me interested in something I had never thought much about before, gave me the information directly and usefully and got me started on a bunch of related questions.

Speaking of which: I had always wondered why more plumbing isn't done with flexible hoses instead of this pipes. Hoses seemed like they'd be way easier to work with. Now my guess is that hoses generally have unnecessary curves no matter what and that this increases the pressure lost. Is that right?
Sergey Brin's Home Page from the Late 90s
Not in the context of computing. Columns are stacked left to right and rows are stacked top to bottom.

https://www.webopedia.com/TERM/C/column.html
I don't know you, but I understand your loss. A wife, a best friend...leaves a big void. Lean on your friends.
4 employees, 4 years ago, before they got their investor that scaled up and sold the business.

They actually had 100s of employees at the time of sale.
not to mention he had his mom who lived nearby do his laundry
Except it doesn't depend on any particular means of communication. You can print out Bitcoin on paper and physically trade it. You can embed it in an image and trade that. You can physically scan QR codes on each others phones to transmit it. Bitcoin and other cryptos can be transferred via sat phone. The Internet and exchanges are just conveniences.

There are also numerous projects to work around Internet censorship in the crypto space. Such as the Substratum Network (https://substratum.net) and Mysterium Network (https://mysterium.network).
My point was that the protocol is superior to Slack in general. Whether you have a use for those features is a different point -- those features are clearly already useful to quite a few people.

But to answer your question, self-hosting would be useful in making sure that internal communication isn't shared with a third-party. e2e could also be useful (depending on what you work on) if you want to just use the public servers.

Not to mention that you can use Matrix like bog-standard instant messaging (replacing the need for other messaging applications through bridges), where those sorts of features are also useful.
“The Evolution of UX Process Methodology”
As a Texan of color with relatives all over the state, I believe a lot of Texans don’t care about skin color AND a lot of Texans don’t care about discrimination based on skin color. So as an immigrant of color, you might be better off in a society where the supermajority actively espouses inclusion (even if they don’t practice it well).
Author works for a major newspaper publishing conglomerate... what is going on here?

Quote from blog About Me page:

>Currently I work for Hearst Digital Media [https://www.hearst.com/magazines/digital-media] to help building enterprise media platform.
How to Copy UHD Blu-Rays to Blank Blu-Ray Discs
Not the OP and not blind, but I've worked with a blind programmer before. You move your cursor in the code and it reads you the line. The screen readers can be adjusted so that the speed of reading is really fast. To someone who is not used to it, it sounds like gibberish. But it's pretty amazing how fast the speech can be. After that, it depends on the editor. My colleague used vi (this is a long time ago -- before there was a vim) and was at least as productive as me. The main thing is that you have to remember the code.

I've occasionally tried to set up a workable system so that I could program blind. I have vision problems where I get ocular migraines unless I have my system set up with a huge font and very high contrast anyway, so I often think that it would be nice to program without looking at the screen. However, I have yet to get my system set up in any way that works. Accessibility has a long way to go. Every time I've tried to set things up I wonder how a blind person can possibly get to the point where they can even start. It's so frustrating.

Actually if anyone in the know is reading this, I'd appreciate a pointer to the easiest to set up Linux system. I wouldn't mind giving it a try again.
I work with time a lot and have always advocated running practical simulations, especially over year changes, leap year changes, leap year days, etc. with the junior engineer I mentor as well as the hardware company that partners with us -- it's only recently after we got bitten by a time-based bug that people have started listening.
It's okay, some hacker will save earth in the end by typing commands into a graphical, 3-D version of OpenSSL 1.2.
1. I think this is the idea behind convolutional neural networks. You learn individual features in the image in the convolutional layers, and you learn their arrangement in the subsequent layers. It turns out that networks don't actually do that AFAIK, but that's the idea as I've been taught it.

2. You can't think of these features the same way you think of features in a linear model, or something like that. This is typical for a neural network.
It’s a trade off of power for water. If your house is entirely local solar what’s the issue?
So let me see if I got this right. The US is in a mighty struggle to stop the expansion of communism, a communist faction takes control of Cambodia and proceeds to kill one in four people, and this is US’s fault?
Someone needs to tell her about processing and get on a modern machine.
The second half is important too: that the expected profits are from the efforts of the promoter. In other words if a company is doing work of some kind, and they are selling a token on the basis that it will go up in value due to the work that they are doing, then it is a security.
if you aren't already very familiar with c, i would say the learning curves for c++ and rust are pretty similar. it will take you longer to get stuff to compile in rust, but correcting instances of undefined behavior in c++ can also take a long time in c++.
Something like that. Certificates aren't supposed to stop working just because they've expired! That would destroy all abandoned or poorly maintained software within a couple of years.

This problem is deeper than forgetting to update it. It should never have caused a failure in the first place. Just the fact that the device apparently can't function at all without the internet is a problem too.
> Nearly 50 languages are indigenous to that one region alone. Not dialects. Languages.

I am a native Indian, born, raised and living there (I mean in India). I find it hard to process this claim. I am pretty sure there are about 10 languages in any fairly diverse region of the country, but beyond that what we find are mostly dialects of various languages.

I am not sure if you are a 'western mind' (as you self identify in a later post) of Indian descent and whether you made that claim based on reading about Indian languages or by interacting with locals and asking them if they spoke languages or dialects. You see, almost all Indian languages (AFAIK) lack words to distinguish the concept of language and dialect. For academics sake, linguists do use some words but they haven't trickled down to general public. The tendency is to use the word 'bhasha' (or its variations such as bhashe, basai etc), which just means 'language', for both language and dialect, and even for such ideas as register and slang. So, any claim made by the general public about they speaking a different 'bhashe' must be evaluated properly and not taken at face value.
> coding is about jumping around so quickly and needing to be able to scroll and grok at high speeds

I mean that might just be how you code, and GP does not code that way...
plenty of c++ is just functions wrapped in namespaces. namespaces alone are a significant advantage over c.
What Does It Cost to Be Big on Instagram?
I don't know for a fact how they manage it, but I bet the feedback is slow enough (those generators are heavy, and it probably takes a few cycles to even accurately measure a change) that they might not have to do much in the way of actively managing that feedback. The system will oscillate a bit (as it did in that video), but there's nothing inherently wrong with that, as long as it's within a certain set of limits.

(And really, the load changes are typically more gradual. Even "everyone just got home from work" is a fairly spread out event, compared to, say, the sudden loss of a few hundred MW of generating capacity...)
I'm currently rewriting our company's customer-facing web app with this stack, as well as the GraphQL backend. I have to say its an amazing experience so far. IMO it greatly helps facilitate readable and maintainable code, on both ends of the stack. Having a strict, self-documenting contract between frontend and backend is the biggest selling point for me.

Coming from a heavy-client implementation using backbone models, or in another instance Ember Data with JSON-API, React+Apollo feels like a breath of fresh air, and simplifies my life to the extent that I wonder why I get paid so much to do what I do.

I would suggest looking at Github's API explorer (https://developer.github.com/v4/explorer/). You can assemble graphql queries in there, inspect the results, and copy/paste the exact query into an Apollo component to make your own app.

REST is still a bit simpler to implement on the server side but once you have the GraphQL API built it is infinitely more maintainable when you're working with multiple teams, and API consumers, each with their own needs and focus.

One weakness I've observed is that since each attribute of an object can make its own DB query, you can have a situation where a single GraphQL query can create dozens, or even hundreds, of individual DB queries, creating a performance issue with a naive implementation. This is mitigated with libraries that batch requests transparently, or with clever structuring of your schema that groups similar attributes into one query.

Also, tree-like data structures are not well supported (like a comment thread, where comments can have replies that recurse infinitely. GraphQL straight up doesn't do that)

However I think that the benefits outweigh the weaknesses considerably.
> I do know about Kotlin Native but that's far, far future

If you mean adoption, sure, but from using it a good bit lately, I'd say the tech is basically there.
While i like folks from Matrix i actually tried to integrate my messaging platform with Matrix and failed. Matrix API is sooooo sophisticated, they are doing something to simplify this, but all this at alpha stage and too opinionated to use it universally. Even XMPP is better in terms easy of use without mentioning IRC (that is dumb simple).
That's really helpful to hear. Thanks very much, and I hope computer science serves you well.
GE aims to enhance solar, wind power performance with new storage platform
cobinhood takes security very seriously..
The expiration date is the fallback if you don't have confirmation from the timestamp server that it was signed prior to expiration.

Ideally it's not used except by the timestamp service, but it seems like a fairly reasonable fallback.
No way, English is too dry and limiting due to the lack of emotional tones that are present at least in Spanish and Russian (because of the flexibility of words and their order in a sentence). I'm ok with using it for technical purposes but I would prefer something else to actually talk.
Why don't we count stack frames in kernel space? And what do we have in JVM underneath us? And libc/Win32 layer?

You even mentioned it yourself: this is the additional overhead added by the Java ecosystem on top of what may already be a pretty large stack of stuff. (From what I've seen, libc is pretty shallow. The majority are either leaf functions like strlen(), or <5 levels from a leaf/before execution disappears into a system call.)

Even if the overhead is not much to a machine, it is certainly going to have an effect on the human who has to figure out what's going on. When you write such code you may not think this way, but every piece of code is a possible place for a bug to be.

From my short experience with Enterprise Java years ago, such deep callstacks are usually symptomatic of code that does far more indirection than actual work --- hundreds of tiny methods that have maybe a statement or two and then call another one. I understand that it might feel good and even better to write code like this, but that simplicity is deceptive: you aren't looking at the whole picture and just focusing on micro-simplicity, when it's macro-simplicity that really counts.

This means that when you're trying to track down a bug, the "interesting parts" are scattered in tiny pieces across dozens of files, and it increases the cognitive overhead significantly in having to piece everything back together. You might not realise that something is wrong until you're deep inside, and then you have to jump back several levels above in the callstack to figure out where things went wrong, seeking in and between files to trace out the execution flow.

I'm glad I don't work on code like this anymore.
> Starting in the next release of Android, some non-SDK methods and fields will be restricted so that you cannot access them -- either directly, via reflection, or JNI. If you try, you can see errors such as NoSuchFieldException or NoSuchMethodException.

Yes, how is this done? Using SecurityManager or something similar?
But how does it sanely pronounce things with abbreviations or even something like:

NSDictionary *myCompoundedWord = @{@“key: [NSNumber numberWithInt: 7] };

And know that it’s missing the terminal “ in the string and has an extra space after the ]?

Seems very difficult. Would be great if it could understand the language enough to verbalize it at a higher level.