__ryan__

Again, not exactly the same as Hydrogen but there’s definitely some overlap in use cases and VSCode’s Jupyter Notebooks is pretty good. You should give it a shot and see if it’s a viable replacement for what you were using Hydrogen for.

This showcases the UI a bit if I’m not being clear: https://code.visualstudio.com/learn/educators/notebooks

I don’t think it ticks every box for you, but have you tried Jupyter Notebooks in VSCode[0]?

[0] https://code.visualstudio.com/docs/datascience/jupyter-noteb...

No.

  Are there any workarounds?

  There are at least two workarounds to the problem. But essentially, they both do the same thing: take the macOS Finder out of the picture, and copy the UF2 to the virtual volume without involving those pesky extended attributes and additional resource forks.

Let’s be real, they’re simply making a case that 1TB/mo is far from abuse as far as an unlimited, capless internet service should be concerned.

Did these starlink customers agree to a contract saying this could happen? Probably. That doesn’t change the fact that it’s a pretty low threshold* when compared to unlimited.

*edited from cap

  at an average of 6-8 per company

  let foo = (bar) => {
    let {a, b, c} = bar
    return [bar, a, b, c]
  }

    foo({ a: 1, b: 2, c: 3 }) // => [ { a: 1, b: 2, c: 3 }, 1, 2, 3 ]

  let foo = (bar) => {
    let {[1]: a, [2]: b} = bar
    return [bar, a, b]
  }

  foo({ 1: "hi", 2: "world", 3: "!" }) // => [ { '1': 'hi', , '2': 'world', '3': '!' }, 'hi' 'world' ]

And they should choose possible homelessness?

  /^[^@\s]+@\S+$/.test("john.\"@\".doe@valid.example") == true

Second, the author was using that as an example of Java showing a pattern of adding syntax improvements, which again might be something that maintains popularity.

Finally, from the article:

  But let's talk about the Java we have today, not the one coming in 6 months.

  Check that its a string containing '@' with at least one character before and after the @ symbol is usually the only sensible thing to do.

So DB."SELECT * FROM Person p WHERE p.last_name = \{name}" would basically be a function call like DB("SELECT * FROM Person p WHERE p.last_name = ", name), which would do the right thing to parameterize the SQL.

  The problem with PWAs is they will never gain parity with the functionality of native development.

Of course, these emails may not have been delivered to OP for one reason or another. If that’s truly the case, it could be a technical error on GoDaddy’s side, or a filtering/mail issue on OPs side.

> I do not believe that printing ‘hello world’ itself should be slower or faster in C++, at least not significantly. What we are testing by running these programs is the overhead due to the choice of programming language.