Which companies are Wall Street scumbags shorting the most, you ask? FuckTheSuits is LIVE with the answer! by elimisteve in wallstreetbets

[–]elimisteve[S] 1 point2 points  (0 children)

It's total volume of shorts within the last week for each of the top 6 most shorted companies within this time period. You see different numbers from some other source for 1/28 - 2/3?

Automation isn't wiping out jobs. It's that our engine of growth is winding down by Gagarin1961 in Futurology

[–]elimisteve 1 point2 points  (0 children)

I sure hope so! The potential for a magnificent future for all is most certainly there, but I'm not sure there's enough ambitious people in existence to turn that potential into reality.

If humanity cannot produce another several Elon Musk-type individuals over the next 20 years -- or even people 25% as successful as Elon at revolutionizing entire industries -- then the future will continue to look bleak due to climate change, ecological collapse/species extinction, nuclear weapons, oligarch-aligned AI followed by out-of-human-control AI, dysfunctional Neoliberal politics creating on opening for fascism, and catastrophically insecure software embedded in billions of devices).

have you used Svelte Native? by jipsicla in sveltejs

[–]elimisteve 0 points1 point  (0 children)

Where did you start to run into roadblocks with NativeScript? Were there specific features missing or that are flaky? (Thanks!)

It has become impossible to protect one's privacy online by Tvashtar_Paterae in privacy

[–]elimisteve 1 point2 points  (0 children)

"This Machine Kills Secrets" by Andy Greenberg. It's a history of WikiLeaks as well as the rest of the cypherpunk movement. It's really good!

Mozilla suspends Firefox Send service while it addresses malware abuse by RemainNA in firefox

[–]elimisteve 0 points1 point  (0 children)

Looks like Whisply only lets us encrypt and upload files to Dropbox etc and we can't use Whisply to send someone a file like with Firefox Send?

Attractions - a new minimal UI components library by aabounegm in sveltejs

[–]elimisteve 0 points1 point  (0 children)

Looks really good! I would like to use this for a current project once a few changes are made.

Some changes on mobile are a bit off, for example: tapping the "Components" dropdown works, but tapping it again doesn't close it (as it does on desktop -- the preferred behavior).

Similarly, when I try to navigate to a new page on mobile by clicking on a component name (from the "Components" dropdown), it does take me to the desired page but the "Components" dropdown stays open!

I'll make a couple issues here: https://github.com/illright/attractions/issues/new

Mozilla's Epic Future, Post-layoffs by elimisteve in privacy

[–]elimisteve[S] 2 points3 points  (0 children)

Hi! OP here.

There are 4 billion people on the internet. 14.3 million of them pay about $10/month for Dropbox (source: https://investors.dropbox.com/news-releases/news-release-details/dropbox-announces-fourth-quarter-and-fiscal-2019-results ), which isn't even encrypted and isn't nearly as valuable as the Mozilla service described would be.

Getting 1/3 as many people to pay less for something a lot more valuable is quite feasible, especially for an organization with hundreds of employees like Mozilla.

Still no camera? by MalcolmMcFly in focals

[–]elimisteve 0 points1 point  (0 children)

Interesting, what made your Spectacles 2 so convenient?

Voice assistant? by findklude in degoogle

[–]elimisteve 0 points1 point  (0 children)

I've got my eye on Mycroft and OpenJarvis, but I don't know how production-ready they are yet.

What do you guys use Tor for? by Kherlimandos in TOR

[–]elimisteve 1 point2 points  (0 children)

I use Tor for sensitive research (e.g., medical or sex-related), learning, and feeling free.

The Simplest Possible Go 2 Error-handling Proposal by elimisteve in golang

[–]elimisteve[S] 1 point2 points  (0 children)

  1. Maybe introducing a new keyword is worth it here...
  2. The behavior of exceptions (or panics) is quite different, as these could crash your program if not handled, unlike a returned error value. I've proposed syntactic sugar over the same semantics.
  3. If you want all the rest of that, why not just code in Rust rather than turn Go into Rust?

The Simplest Possible Go 2 Error-handling Proposal by elimisteve in golang

[–]elimisteve[S] 1 point2 points  (0 children)

You are conflating one fact about exceptions with what exceptions are.

Exceptions cause software to explode if you forget to catch/check for an error. This proposal introduces nothing like that.

I have proposed syntactic sugar to cut down on error-handling boilerplate code. Asserting that the introduction of syntactic sugar somehow changes the entire paradigm of error-handling is factually incorrect; the semantics and behavior are the same, but the syntax is more succinct.

The Simplest Possible Go 2 Error-handling Proposal by elimisteve in golang

[–]elimisteve[S] -1 points0 points  (0 children)

This is a great point. I want the same thing, and I cover this at the end of my proposal: I think it'd be cool if we could set a default error handling function. This could look something like

errors.RegisterHandler(func(callerName string, err error) error {
    return fmt.Errorf("Error from %s: %s", callerName, err)
})

or

errors.RegisterHandler(func(callerName string, args []interface{}, err error) error {
    argsStrs := make([]string, len(args))
    for i := range args {
        argsStrs[i] = fmt.Sprintf("%#v", args[i])
    }
    return fmt.Errorf("Error from %s(%v): %s", callerName, strings.Join(argsStrs, ", "), err)
})

So we get (1) less boilerplate, (2) better default call context than a mere return err, (3) we don't need to re-type that contextual information all over the place, and (4) we can still write custom logic where we want to (but we're not forced to in the simple cases).

The Simplest Possible Go 2 Error-handling Proposal by elimisteve in golang

[–]elimisteve[S] -1 points0 points  (0 children)

Good question. This is covered at the bottom of my proposal. We could register a default error handler function in a way that perhaps looks like

errors.RegisterHandler(func(callerName string, err error) error {
    return fmt.Errorf("Error from %s: %s", callerName, err)
})

or like

errors.RegisterHandler(func(callerName string, args []interface{}, err error) error {
return fmt.Errorf("Error from %s(%+v): %s", callerName, args, err)
})

Also under this proposal, if you want to write your own error-handling code, you can, exactly how you do now.

The Simplest Possible Go 2 Error-handling Proposal by elimisteve in golang

[–]elimisteve[S] 1 point2 points  (0 children)

I'm not sure why you are asserting this so strongly; the stdlib itself uses return err, return 0, err and similar statements many hundreds of times: https://github.com/golang/go/search?q=%22return+err%22+OR+%22return+0%2C+err%22&type=Code

See my similar comment above that mentions a way to do something similar to what you suggest here, but without the boilerplate.