lmc

Weather data is usually derived from geostationary satellites which is sort of an adjacent field to the lower-orbit imagery the article is based on (i believe?)... but i know of a couple of projects doing analytics here - not sure about commercial potential though, they're early stage startups or academia.

Thanks!

This is what i was wondering that wasn't explained in the article... does UE offer some guardrails for working with c++ that make the jump from C# an easier decision?

This doesn't directly answer your question, but... something to watch out for is experienced developers can also struggle with promises and async code if they've spent most of their career working with sync code. And when we 'get' it, the difficulty of the journey is often understated. This stuff can be hard, so don't sweat it if it seems frustrating. (On the other hand, it may be easier if you don't have years of sync patterns to mentally set aside )

Here's a few. The docs link to some others that may also be useful...

Promise.resolve()

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

You can use this in place of new Promise() (though you rarely need it, as an async function automatically wraps any non-promise return value in a promise.)

----------

Promise.all()

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

For making requests in parallel, and returning when all have been successful.

----------

Promise.allSettled()

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

For making requests in parallel, and returning when all have completed whether successful or not.

----------

Promise.any()

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

For making requests in parallel, and returning the first successful response.

--------

As mentioned in sibling comment, things like fetch and DB calls return promises anyway, so the above are mostly only useful for working with multiple other promises.

Sorry but losing stars by going from public to private is a small price to pay compared to going from private to public - what would you suggest be the guiding hand to prevent that kind of situation?

I had been accruing bookmarks in Google Bookmarks since 2008, then saw it was going to be shut down[0]. I liked the workflow and the core features seemed simple enough, so I made a cheap clone - Strudel Bookmarks [1] (I was planning a move to Austria at the time). The code is terrible so I never open sourced it. Took it as an opportunity to try a couple of pieces of tech out... much respect to Hasura[2].

[0]: https://9to5google.com/2021/07/20/google-bookmarks-closure-m...

[1]: https://i.redd.it/uvrv7qsqtct81.png

[2]: https://hasura.io/

That was my thinking - anything of value is product-specific and behind closed doors. It's not my field, but something I see come up from time to time that seems weirdly over-represented in ML articles.

Makes total sense - the core is the part of the apple everyone throws away.

"An Atlassian spokesperson contacted by The Reg blamed the loss on the failure of “multiple” storage disks at its cloud storage provider on 28 April."

10 years ago to the month.

So as long as everyone plans a vacation for this time in 2032 it'll be OK.

Much of the field seems to be fixated on throwing massive compute resources at models with results that can neither be evaluated nor reproduced.

"the Recommender Systems research community is facing a crisis where a significant number of papers present results that contribute little to collective knowledge […] often because the research lacks the […] evaluation to be properly judged and, hence, to provide meaningful contributions"

https://doi.org/10.1145%2F2532508.2532513

More here... https://en.wikipedia.org/wiki/Recommender_system#Reproducibi...

"Please do not spread fear, uncertainty, and doubt about security without precise details."

I read the FAQ several times before posting, and it still didn't answer the security question. Elaborating my concerns...

You suggest developers use this. That means, users will most likely be running dev servers. Dev servers, especially in the NodeJS world offer the ability to connect a debugger.

What happens when someone spams requests to connect a debugger to bore.pub:<PORT>?

> This will expose your local port at localhost:8000 to the public internet at bore.pub:<PORT>, where the port number is assigned randomly.

Port numbers are limited to 65535. Isn't this un-scalable and a massive security risk?

Or, quit Facebook and avoid needing to use any natural resources at all.

The MDN docs say this about Crypto.subtle [1]: "Warning: This API provides a number of low-level cryptographic primitives. It's very easy to misuse them, and the pitfalls involved can be very subtle.

Even assuming you use the basic cryptographic functions correctly, secure key management and overall security system design are extremely hard to get right, and are generally the domain of specialist security experts.

Errors in security system design and implementation can make the security of the system completely ineffective.

Please learn and experiment, but don't guarantee or imply the security of your work before an individual knowledgeable in this subject matter thoroughly reviews it."

There are many ways to fuck up using this. A couple of concerns about the article - I see no mention of a secure nonce, and no mention of CSP. I'm not a security expert, but I'd be very wary about using the code here.

[1]: https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypt...

Yes. Think of desktop as many thin slices of the cake.

Got it, diagrams are part of your product, rather than for system design.

Take a look at Structurizr - https://structurizr.com/

The guy that makes it is super helpful on twitter as well.

Ah, I've just realised, the article above pointed to a quote by Simon Brown - he is the Structurizr guy :-)

¡Sí, que cabrón!

Please, put an id on the HTML element, and a CSS rule targeting that id, rather than use !important. !important really was a mistake and should only be used to counteract other uses of !important you don't have control over.

> important was added for one reason only: laws in the US that require certain text to be in a given font-size. !important stops the cascade from changing it.

But it doesn't. !important begets more !importants.

Nice to hear the reasoning behind it, but it's a PITA and should never have been added.

I'm trying out Upstash for this - https://upstash.com/

Are there any tutorials you could recommend please?

Fantastic, this is all really useful info. Thanks very much.

Perhaps this is something that could be fixed with a tooling, rather than language change? E.g. Syntax highlight a different a colour if it's the first use of a variable.

Jose Storopoli (@storopoli): "I've made amazing friendships here, co-authored a free open access and open source Julia Data Science book with Rik Huijzer and Lazaro Alonso."

I just read this book. Every page was like, 'wow'.

A couple of questions I had afterwards:

* I saw the DateTime type, but it doesn't seem to have a timezone - how do you deal with timezones?

* How is it to work with async code?

* It's a garbage collected language, what are some techniques to avoid performance pitfalls due to that?

If there's other Julia programmers around, any answers would be much appreciated!

Me too bud. Glad you found a good place to work.

It might be easier if we stopped considering twitter and instagram as suitable places to publish nuanced, serious stuff that was liable to misinterpretation and misrepresentation

Good points, and good to see there's some data behind that as well. That's how it's seemed to me in my areas. I'm not sure to what degree it applies for things like psychology - prob never as extreme as my original example, but it would be interesting to see a similar study.

The UK is no longer in the EU and the new visa requirements have kicked in :-(

https://www.gulbenkian.co.uk/can-eu-citizens-work-in-the-uk-...