skysight-inc/HackerNews huggingface dataset:
How do you describe a developer tools?
Please help. My boss is killing me with this.

Our product is a developer tool. We're trying to give the landing a page a clean and direct value prop. I don't know whether or not to make it address the "why", "what", or "how". Furthermore, I don't know which would be the most valuable to developers trying to understand what we do.

Currently, we have "Develop Smarter, Developer Faster". I totally hate that. It's vague, assumptive, and tells NOTHING about what we are. I suggested, "Accelerate app development using technologies that scale". I'm not crazy about it either, as it's also not direct.

However, I'm not sure whether we should be super explicit, like "Leverage GraphQL + Serverless in data-driven SaaS apps".

Any guidance would be welcome!!!
Presumably they also have a veto, at least, on Firefox development as they're paying handsomely for it?
This is a great comment that accurately (and nonsensationally) depicts what it’s like to live/grow up in a hurricane area.
The issue of having to trust the server also applies in a lot of non-browser cases. For example, I have to trust the 1Password update server, or forego 1Password updates.

It looks like the issues with browser-based cryptography from those two articles fall into three broad groups.

1. You have to trust the server.

2. The browsers don't do a good job of letting a site's JavaScript keep things secret from other things running in the browser.

3. If you implement cryptography in JavaScript, you are probably going to screw it up. There's a lot more to doing it right than just knowing to use AES and whatever the currently favored hash function is.

#1 is probably acceptable in a lot of cases, and #3 can probably be addressed by using the Webassembly version of libsodium.That leaves #2 as the apparently insurmountable issue.

Suppose the user was willing to create a separate Firefox or Chrome profile just for using my web-based app, and did not install any browser plug-ins under that profile, set its home page to my app page, and never used that profile to visit any other sites.

How close would that come to dealing with #2?
I get that occasionally at work as well - but I find the main hindrance at work to be the distractions of the open office..
Firefox 57 launched at the end of 2017 and was very much a love-it-or-hate-it change. Some people saw a significant performance improvement and that was important for them. Other people didn't have a problem with its performance anyway but saw the entire ecosystem of extensions that made Firefox different thrown under a bus.

I'm firmly in the latter camp, and if it weren't for the security implications I'd still be running pre-57 Firefox with the full set of extensions I found useful. If I didn't need to use all the major browsers anyway because of my web development work and I wasn't so untrusting of Google in terms of privacy, I might easily have decided at that point that Firefox no longer had any compelling advantage over Chrome and switched. Presumably some people did.
Will no longer support
You misread the suggestion.
Emoji Driven Development in Ruby
Seriously. I already know everything in the aricle (because I've read similar before) and yet I still have trouble remembering it when reading a map and trying to visualize the area I actually care about. I can't imagine how the heck purple are supposed to just deal with this and wrap their head around it, especially regarding an emergency.

I'm wondering if the people who didn't prepare due to a misleading map despite a technically accurate prediction can sue for damage? Not that I would enjoy seeing NOAA et al. in a lawsuit, but if nothing else has gotten them to fix these, maybe a lawsuit will?
If you're talking about ES File Explorer, I spent the last month trying out other apps and in the end just downloaded an old ES apk lol
Right.

It doesn't work for anyone.

I'd love to see a city that had like, a super dense core, then a ring road with endless car parks around it or something like that. You drive in, from your country home, get the subway for 10 mins from the ring road to the CBD or your urban dwelling friends' place, sorted.

Zone the ring road to kill sprawl.

Ban cars inside the ring road other than trucks for deliveries, workmen etc.

Best of both worlds.

It's not gonna happen in a pre-existing city though, the winners will block it (and rightly so).
Thanks for the information!

Yea... libraries are always good (especially for math and analysis), but I find that powerful languages need far fewer libraries to get things done. APL can do something with a few characters that might commonly be implemented as a lengthy function or library in some languages.

Windows Powershell can surprisingly do a lot of what Perl 6 can do and people mostly understand the limitations. You can automate processes, build your own DSL, have full OO support, full .NET interop, concurrency, you can pipe data around kind of like with FP...etc. It doesn't have some of the more perlish features though.
"will no longer be supporting" is completely fine, though.
> Idealized solution: A temporary bypass zone is communicated to the self-driving cars.

There’s so many great opportunities like this once the cars are self driving and connected. For example, a ten lane highway without dividers! 8v2 split depending on the time of day and traffic patterns. How many times have you been stuck in a lane with the other lanes in the other direction completely open?
I wasn't aware of any browsers having epub support. Additionally, the practice of using browsers as your OS is bad. Native applications are the way to go. Pdf support should also be removed from all browsers.
And you have to wonder how Google makes their billions.
You can link a Rust library to a C/C++ binary and you can link a C/C++ library to a Rust binary. https://doc.rust-lang.org/nomicon/ffi.html

Notably you need to use the C ABI to call things from C++ as Rust FFI doesn't support C++ directly.
Yes Waze is great on Apple carplay.
Perfect Speed camera warnings are a lifesaver here in Europe.
All that withstanding, nobody but developers buy Microsoft products because of VSCode.
This applies if you're well-off, but the less wealthy don't get a choice in mobility. If you don't have money, a secure job, housing, car, etc, mobility is quite limited, costly, and time-consuming (if it exists at all). Others' increased mobility can even hurt the less well off (see: white flight). That hurt then becomes a burden on everyone, as it manifests as poverty, crime, unemployment, over-reliance on public services, and so on.

But increased accessibility reduces those problems, because it becomes less difficult to do things people need to do, regardless of socioeconomic status. You have the option of being mobile, but you don't have to be.

Now, getting more specific to the OP: traffic congestion is due to inefficiency. Adding lanes/roads doesn't address the source of the issue: cars are inefficient mass transportation mechanisms. Traffic jams only occur when large masses of people are transporting themselves. You can either A) add more mass transit, or B) bring the services closer to the people, so they travel less.

The latter helps the traffic jams, but it also helps people who don't even have an option to be in the traffic jam. Mobility helps the well-off, accessibility helps everybody.

(downvote away, you know i'm right)
Because that's the system under which we live.

Healthcare should be provided to all by the government for free, but until then we must live under the system.
I was stating a syllogism there: understanding and working with different coding styles is difficult, increased difficulty adds increased expense, and Perl supports many different coding styles.

As far as I know, nobody's done a comprehensive cost analysis of similar software built using different languages, methodologies, or architectures. Certainly nothing recent. I've harped on this before quite loudly and I think it's one of the reasons our industry can't be called "engineering".

People's individual experiences just don't make for good enough data because there are too many confounding variables.
> What architectural problem justifies doubling the number of requests?

Simplicity. If I create some "component" that declares what its data from the server needs to be (some subset of the domain), then it knows how to read/load the data to display (query). The component can do any commands where the user wants to change some domain entities/state and I don't need to care about figuring out how to update my local state with some response from the individual command. I can just ask the server "give me the updated state", which is the same subset of the domain you declared for that component. There's much less chances for things to go wrong in this design since there is only one code path for updating the components state.
Well, yes? You can drive and think about other things–honestly, I wouldn’t believe you if you said you don’t do this in.
Meanwhile we all keep ignoring that the booze industry has worked tirelessly to make sure we use the phrase "drugs and alcohol" so alcohol isn't recognized as a drug by most of the population
Both can be true, but if society has already spent a lot on one, than it can be much much more efficient to gather the low hanging fruit on the other.
This makes it seem like the brits have trouble plugging things in, that can't be right.
I've never had a power cord get "hot" either.
> And tell them how to prepare.

Exactly. I made a comment above that mentioned the mass migration to the coasts means that many people do not have years of experience dealing with hurricanes. What you just said is common sense for you and I, but may be a complete unknown to someone who just moved from NJ or Ohio.
We are using JIRA's cloud offering and it's the slowest application I use. It's slow enough that I don't care about any of the other (pretty glaring) UX flaws.

It often takes more than 2000ms to switch views (e.g. just to switch from looking at an issue to the board showing list of issues in the current sprint for my team). Sometimes, 5000ms plus.

It's so slow that I've noticed everybody does what I do, namely ⌘-click all links so that they open in a new tab. That way you don't "lose" what you are currently looking at, and have to endure another 2000ms load time just to see it again.

Everybody's JIRA window has like 40 tabs open by the end of the day.

One result of this, beyond being irritated, is that meaningful bug discussion never happens on the ticket comment threads, the way it used to with GitHub Issues, or the way it would happen if JIRA was as fast as a normal app (like, say, GitHub Issues). The discussion is all on Slack now, completely separated from the issue tracker and super hard to find when you need it.

I occasionally manage to paste a few Slack links into JIRA bug comments, since I already have that tab open and I know nobody else will.

We didn't love the feature set and UI of GitHub Issues, either. (Hence the sadly failed search for a new tool that resulted in JIRA.)

But it wasn't slow, so people did actually use it. I don't think we have a features/UI problem with JIRA. If it was fast, I think people would use it about the same as they did GitHub Issues.

But it is slow, so engineers use it very minimally: create an issue (which is usually done via our Slack chatbot, because using the JIRA UI is so annoyingly slow that somebody wrote a bot to automate that), put the issue into a sprint, and then close an issue when it is finally done. Those are the 3 operations we do.

I think the project manager people are OK with JIRA, because they mainly use it to generate fairly complex reports that admittedly are pretty useful to see how we did in the past iteration compared to our goals. That is SUPER SUPER slow too, but they don't mind as much because it's a bi-weekly thing they do, not something they do over and over throughout the day.

I think JIRA has a variety of other usability problems, but the deadly slowness outweighs all of them combined. We still "use" JIRA in the sense that it's the system we use to track bugs. But we don't actually use it much at all — because it's slow.
eoma68 is trying to do that. It's definitely run into some issues though.

https://www.crowdsupply.com/eoma68/micro-desktop
True, but the point is, making pipes big enough to actually make this work ... is physically impossible with current constraints.
How did humanity survive when none of this was even possible 20 years ago?
Here's a thought experiment I like to use whenever this comes up.

If someone were to approach you on the street and ask you to do something for them that will take an hour of your time, what amount of money do you think would be a fair compensation for just the time expense? Now add to that the fact that it's not just an hour of someones time, it's also an hour of use of an expensive machine they own and maintain.

I've found that when minimum wage is thought of in this way, anything less than $20-25/hour sounds absurd.
I never really learned screen because daemonised emacs sufficed for me. My daemon uptimes are normally the same as my system uptimes, with the one on my VPS currently at 77 days.

A few years ago, I started using one daemon per project with server-use-tcp, each with a slightly different theme so I can easily tell them apart.

(posted from emacs-w3m)
It only requires that amount if you’re intent on living in the most expensive cities in the entire country.
I think I remember Doug Crockford talk in which he laid out the original design of EPCOT. It was very similar to what you described.

Found it: https://www.youtube.com/watch?v=JvoCIPKWobs
EPUB is based on XML if I recall, so needing a third party app to view them seems burdensome.
“Give me directions to foo” - gives directions to foo in apple maps

“Give me directions to foo using Waze” - gives directions to do using Waze

This might be new, but it definitely works on the iOS 13 beta, although I’m pretty sure it worked on iOS 12. It would still be nicer if we could just set default apps
“support”, as the author of the article suggests, should replace “be supporting”, not just “supporting”. The simple future is called for, not the future continuous.
About 9.5% on desktop, and 4.5% globally.
That sounds like an equally valid criticism to me, but if you're sense of prudence suggests that some people might not want to hear it from a dude, so does mine. It's understandable that people sometimes feel like their being attacked en masse by outsiders when we talk about this, but I think we're better off if we're able to talk about it civilly.

Looking and dressing "right" is hard for some people. Approaching our expectations with a more removed perspective helps, but does tend to sound clinical. For what it's worth my gf complains about this kind of stuff in a way that sounds similar to me, but using somewhat less high-brow language. :)

EDIT: I asked gf what she thought of that paragraph: "meh i don't give shit it's fine." Then I asked if she thought a man could get away with saying it: "probably not on the internet LOL". n=1.
>So they should start losing money?

I was unclear; their revenue streams are still overwhelmingly comprised of proprietary tech.

Darwin and AOSP are massive compared to the toys MSFT is throwing over the Linux wall. This idea that they need to lose money is a strawman.
Why Dragon Quest Failed to Make It in America 30 Years Ago
Hate the font
Agreed. I'm on an iPhone 8 now, which is fine. I don't want FaceID.
I had to hack Hyundai's website to keep my navigation and monitoring service. I bought it used 3 years old in 2016. At that point they had already removed the ability to purchase updated maps. Then this year I got an email saying the navigation and monitoring services would be unavailable for renewal. The renew UI was disabled, but I reverse engineered their API, crafted a request, and got a system error. To my surprise my subscription was renewed. There is no reason I can think of to discontinue these services other than to goad me into purchasing a new car.
There's a scientific field I never heard of: Corporation Psychology
Someone has to open it. Someone has to key it into a billing system. Someone has to scan it. Someone has to archive it. Some process needs to occur to verify that the payment indeed went through.

I doubt their remote deposit app is any less clunky than the consumer one they give me. If it’s better, they’re paying for it.

Someone needs to manage those people. And they need space to do their work.

I could see it taking 15 minutes in total labour costs.
Right, because it's clearly the domain name I take issue with, and not at all the literal lies that have been published under it.
Any plans for a unified inbox? I’ve two email accounts and switching between them in Consider is a hassle.
This is what I think has happened, some employers do ask for all IP still. But others use the term inventions to make it seem like they aren't as over reaching. But generally I have seen that they do define "invention" in the document to basically include all IP still.

This is one that drives me insane, and I just won't touch a company that is doing this as it is unreasonable and so evil to me. But sadly a lot of startup legal firms put this in their standard IP documents for employees to sign and if you don't catch it you can be screwed.
Unfortunately - I think what you're seeing here is that people here (especially in this article, on HN, and in general) are not focused on the "driving experience" but more of the "commuting experience". People are not using these vehicles to /drive/ but to /commute/ or just get to a destination. They're no more engaged in driving than they are in flying when on an airplane.

I think the audience for these things are people stuck in bad commutes or long boring trips where they are unengaged from driving.
If we want to show people a probability map, why not just show maps for "probability of necessary evacuation" or "probability of serious structural damage" or similar? Instead of probability of hurricane center path or whatever that nobody cares about?
So on my Mom’s recent Honda we’ve (accidentally) discovered that pressing the volume knob like you would to turn off an old radio plays/pauses what you’re listening to.

Give that a try on any car you look at, you may find it works.
You could open up lanes a quarter mile at a time even depending on traffic demands.

Eg. Between exit 1 and exit 2, 8 northbound lanes are open. Between 2 and 3 we have 6 northbound lanes.

It's would be pretty disconcerting to travel in your self driving car and head full speed into oncoming traffic only to shift lanes a few moments before collision though.
Looking into this only briefly, it didn't take long to find a lot of very questionable decisions made by Brave:

1. They're positioning themselves as both an advertiser and a privacy advocate[1], which strikes me as more of a strategy for bootstrapping revenue than a trustworthy moral position. The entire point of crypto micropayments is to pay for content with crypto rather than attention/privacy. Why should I view Brave's ads rather than the other ads on the internet from advertisers who also claim their ads respect privacy? The fact that Brave has decided to get into bed with advertisers at all shows they're committed to profit, not to users: micropayments are just a way to diversify for Brave, which will quickly fall to the wayside if it fails to provide the revenue they want.

2. The entire concept of a Brave Verified Publisher stinks. It positions Brave as a censor. If this system takes off, then suddenly Brave has control over who gets paid for content on the internet, and can censor content they don't like. And this isn't hypothetical, they plan to do this: their TOS[2] explicitly contains a code of conduct which contains a long list of things they will terminate your account for: they promise to use their power as censors to enforce of US copyright/patent law and also a wide variety of subjective social norms. This also shows their commitment to being an advertiser rather than an application that serves users: if you're serving users then you let them pay for the content they want to pay for, but if you're serving advertisers, then you can't let advertisers brands be seen as supporting questionable content.

3. BAT based in Ethereum seems to be basically a way to ride the wave of cryptocurrency hype while still positioning themselves as a central authority/middleman. If they weren't trying to position themselves as a middleman, they would just make the micropayments in Ether directly, or better yet, in a cryptocurrency that doesn't have a history of forking the blockchain to fix an bug in a major users' contract[3]. If they weren't trying to ride cryptocurrency hype, they'd just allow micropayments via a much-simpler-and-more-reliable REST API or similar since they're already the central authority anyway.

I don't think we can trust Brave with our privacy or attention. I don't think we can trust Brave with the decision of who gets paid for content. I don't think we need Brave as a middleman to pay content publishers. I don't like the state of how content is paid for on the internet, but I don't think Brave is the solution.

It's disappointing to me that Wikipedia has decided to associate their name with Brave's. A big part of why I respect Wikipedia is their long-standing policy of keeping independent from advertisers, and it seems naive of them to have not realized that Brave is an advertiser. I can understand why Wikipedia has made this decision, but I still think it is a compromise of Wikipedia's values, and I hope they'll reverse their decision in the future.

[1] https://brave.com/brave-ads-waitlist/

[2] https://brave.com/terms-of-use/

[3] https://www.coindesk.com/ethereum-executes-blockchain-hard-f...
250 comments yesterday in https://news.ycombinator.com/item?id=20821064
LEGO bricks are known for their very precise shapes (Only the best is good enough); I doubt they will ever change said shapes without good reason (a green 4x2 has no reason to be shaped differently than a red 4x2, and if they were, it would probably lead to minor visual defects that would be unacceptable).

However, an easy way to split by color would be to package bricks in different bags - as said bags have various shapes and textures as well. [0]

[0] https://www.brothers-brick.com/2018/04/16/lego-star-wars-752...
Yep. Honda has been shipping Android based systems since at least ‘16.
It happens after succesfully finishing several rounds.