CraftThatBlock

A big issue I see with this is that having custom classes (the whole extensibility point), at least in TypeScript (without re-declaring them).

I think the original statement that it was "unlikely" was correct, the effort put into this project has been incredibly impressive.

As another poster has said, there's still a long ways to go for support.

RUD was <1km, likely around 100-250m (speculation) from the flash in stream. Debris probably at most a 1km radius around, and this is land they bought and will clean up (obviously).

I agree, but branding for bills is an important part. For example, "The Patriot Act" sounds better than "Spying on Citizens Act"

You can still block those blobs, as they too are loaded by URL.

I don't see this as a large tradeoff. Taking from your example and modifying to follow good practices:

    const launch = initializeLaunch(/* ... */);
    
    const App = () => {
      // ...
    
      return (
        <LaunchProvider launch={launch}>
          <div>...</div>
        </LaunchProvider>
      );
    };

A global initializeLaunch is a deal breaker.

Services should be passed a provider (similar to Redux). Having state stored globally can cause many issues:

- Testing is harder, as the state can be shared

- Having sub-stores is impossible

- Having parallel stores is impossible

The 4950X doesn't exist, do you mean 3950X?

I'm definitely very excited for RDNA 3. I think AMD's GPU momentum is just starting, similar to the 1000s series.

Estimates I could find put it around 30-170Mbps, but the top end (speedtest.net average) of Canada is >150Mbps, which isn't actually common (living in/near large city). Average likely around 30-60 Mbps from experience.

This is a great point - I'll likely make a follow up post regarding this. I've never seen the autoStash option (it's not even on the git-stash man pages/documentation), and definitely very useful.

Edit: I've added a section on autostashing and on the -p flag.

This is a great move forward, but compared to GitHub, this is still very high.

Free -> 9$/m -> 49$/m seems like a much more reasonable pricing. I'm sure more users would pay if fhe price is better.

Cue https://killedbygoogle.com comments...

NVIDIA Broadcast is only available on Windows (but free and works very well if you have a RTX card). Use it if available!

If using Discord, Krisp is built-in. On Windows/Mac, you can also install Krisp standalone.

On Linux, I would recommend NoiseTorch or other similar software.

For me, I think having an option to start when I login would be great (similar to NVIDIA Broadcast on Windows).

This would solve my biggest issue that when turning on and switching my input to it, other programs sometimes need to be restarted to pick up the microphone change.

Otherwise, keep up the great work!

Most malware is likely more popular than the majority of apps this affects.

- Malware can be signed - Popularity != trustworthiness - Software "trustworthiness" shouldn't be depended on. Strong sandboxing avoids malware

An open-source project (from myself) doing the same with WebSockets: https://github.com/Cretezy/dSock

Long fully-random passwords in a password manager is what I recommend to friends and family. Using 32 alpha-numeric is what I use by default, with exceptions when other requirements are needed (symbols, etc). This ensures compatibility with pretty much everything.

62^32 = = 2.27e57

I always say: "If you can remember your password, someone can guess it"

Not really (at least yet, I think). This simply bundles the Deno binary and the script (I think the pre-compiled, as in TypeScript -> JavaScript, then possibly as pre-compiled AST). This is why the output binary size is the original Deno binary + the script size (roughly).

So it's functionally equivalent to running using deno test.js

June 30, 2020 is in the past? Did they mean 2021?

It's very easy to perform very well on a specific benchmark when there's dedicated hardware for this.

I'm not saying this isn't good, it's great for people editing, but this isn't a general indicator of performance (which is reportedly good!)

I've stayed clear of WTFPL because it's not an approved license (https://opensource.org/licenses/alphabetical), even though it does fit it's requirements.

Using a more established license also usually comes with more corporate knowledge.

When I release open-source software, I usually release it under MIT. I don't think my projects are as essential as a kernel where the GPL would shine, and I also don't want to hinder companies from using my software.

BSD is fairly similar to MIT, but I feel like the clauses cause confusion. Ideally, I think 2 or 3 clause BSD are the right choices (4 is fine too, but I prefer it less).

What other licenses are their to choose from? What would be the advantages of licensing under different terms?

I've also been curious if a CLA is a good idea or not, I've implemented it to one of my projects (using a GitHub bot) and it hasn't been a problem, but I'm still unsure about the implications of licensing this way.

I'm also unsure about if Apache would be a good fit.

Yes! You can find my email on my profile

Agree. The databases we're my biggest costs on GCP, and DO offers more for less.

Cloud Run, as you said, is pretty great. In my other start-up, we're using Cloud Run and Cloud SQL, and again, Cloud SQL is the biggest cost (~95-99% of the bill)

I had no issues so far, everything has been fairly smooth. Setup was very easy too (was my first cluster setup), and pricing is very good.

SaaS business single founder here, moved from a mix of GCP's Cloud Run, Cloud SQL, and Compute Engine to DO's managed Postgres and Kubernetes, and it has had the follow effects:

- Much cheaper, reducing bill from >100$/month to ~40$. Important for early stage startups - More performance, easier scaling. Found that my application was much better suited to run in K8S, but this is definitely specific to my use-case - Consolidation of resources. Except Postgres/Redis, everything is in my cluster, simplifying management and maintenance

For my business, this was a great move, but as others have said, I wouldn't recommend it to everyone. K8S is a great and powerful tool, but also is very complex.

You're right, I was using incorrect numbers. An Atlas V's sticker price is 110M~160M, so about 2-3x cheaper

Starship launch price should only be a couple millions (see the article).

<100M is _technically_ right, but very far off. Since Starship will be fully reusable, it's upfront building investment (the ~100M price-tag you are referring to), spread over the lifetime of the vehicle, plus staff/maintenance/fuel for launches.

Falcon 9 was already a +10x reduction (~~1.5B per launch -> ~70M, likely cheaper for reused boosters), and Starship will be another +10x cheaper than F9. This means Starship will be >100x cheaper than competitors (excluding small-sat rockets like the Electron)

You are likely looking at the Intel models

I don't think they included Intel's new Xe or AMD's APU in those 2x for iGPUs.