benmccann

Framework-agnosticism is not an afterthought in Vite, but has been there from the beginning. Svelte has gone all-in with Vite. Go to svelte.dev and the homepage instructs you to create a new project using Vite. We've never run into any problems with things being built for a specific framework in Vite.

Can you describe the process for getting access through your university? I'm curious what that experience is like

Here's one built with Svelte: https://hn.svelte.dev/

It's not exactly an apples-to-apples comparison for a number of reasons including implementation and hosting differences, but might be interesting to people anyway. The code lives here: https://github.com/sveltejs/sites/tree/master/sites/hn.svelt...

One of the coolest projects I've seen built with Svelte!

Do you have a link to the proposal?

It seems somewhat unlikely for a number of reasons. The article was quite long, so I didn't read it all, but a key takeaway seemed to be "Gatsby only uses the server-side rendering APIs when building for production". SvelteKit does SSR rendering in development as well, so you wouldn't have the issue of dev and production being different in that way. Also, Svelte's hydration works a bit differently than React's.

But React isn't just JSX. It's also the entire runtime library, hooks, event handling, forms, state handling, etc. The example you shared is a bit too simple to understand where Svelte shines because it doesn't introduce any of those concerns.

By having it's own templating language, Svelte is able to compile the templates to JavaScript in a way that addresses many of those concerns in a way that I think it easier to deal with as an end user of the framework.

If Svelte were using JSX, I don't know that it'd be possible to do everything else that it does so simply because you can write anything that's valid JavaScript in JSX whereas Svelte has just a couple of basic control structures that its compiler can parse and convert to runnable code.

I'm doing my own thing and won't be joining any existing company ;-)

As a heavy contributor to SvelteKit, I can't see a loss in neutrality happening. I personally use other hosting platforms frequently with SvelteKit, both Rich and Vercel have expressed they want to avoid this outcome, and other SvelteKit maintainers work full-time at Vercel competitors and also wouldn't let that happen ;-)

> Fixing dev server errors is a little distracting at times

You will be very pleased with the upcoming release of Vite 2.7! It's by far the most impactful release of Vite thus far for SvelteKit. All the major known issues we've been tracking have been addressed in the latest Vite 2.7 beta (assuming that one of the PRs we're still working out the kinks of doesn't get rolled back, but either way it'll be a huge improvement!)

They are called "forever chemicals" because they don't naturally degrade in the environment. That term does not refer to how long they stay in your body. Because they are don't degrade in the environment, the amount found in the environment is continuing to increase: http://marinespecies.org/introduced/wiki/Polyfluorinated_com...

That FAQ was rather outdated. I've updated it to hopefully be more helpful. Thanks for pointing that out.

There are numerous ways to compare voting systems. There's a good selection of comparison methods on this Wikipedia page: https://en.wikipedia.org/wiki/Comparison_of_electoral_system...

The project hasn't really been publicly released yet. The repository is still private. The package is up on npm, but isn't ready for widespread adoption yet. I'd recommend sticking with Sapper for now.

https://www.npmjs.com/package/@sveltejs/kit

"Sapper is dead" is not really accurate. SvelteKit is Sapper + Snowpack and there will be a migration path.

The services provided by the government have not been stable over time and have dramatically increased

If you're talking about single family homes - that's a property tax, which is not what people are normally talking about when they discuss a wealth tax

How does this compare to Tailscale? It's nice that Twingate has a Docker image available, which is something that Talescale is missing

The VS Code extension will surface type checking errors for you or if you want to surface them on the command line you can run https://www.npmjs.com/package/svelte-check

Here's one chart I found showing the relationship between disability and unemployment statistics: http://www.mybudget360.com/wp-content/uploads/2012/05/trimta...

You need to apply to attend. The application has already passed for this batch (https://apply.ycombinator.com/events/246), but you can check back later to apply for the next one.

I believe Room and Board offers sofas without toxic flame retardants

Here's the WHO report for folks who are interested: https://www.who.int/water_sanitation_health/dwq/nutrientscha...

There's a plugin for Chart.js that does something similar was well: https://github.com/nagix/chartjs-plugin-rough

You can use chart.js without moment. You do not need any date library if you're not using the time scale. If you are using the time scale you can also choose date-fns or luxon as lighter weight alternatives.

It looks cool. The only examples I see though are for drawing maps. Any pointers on how you could draw a x/y chart?

There's a Chart.js plugin that will do that for you as well: https://nagix.github.io/chartjs-plugin-rough/

I think most chart libraries use SVG. There are trade-offs between the two approaches and both have their advantages. One of the places that canvas really shines is performance. In the past I've found Chart.js and some of the faster SVG libraries to be about on par with each other, but the upcoming Chart.js 2.9.0 release has had a couple major performance improvements that I think will make it significantly faster than probably any SVG library. It's an area we'll continue to work on since it's one of the main reasons to choose a canvas implementation over an SVG implementation.

I think the other advantage SVG has can be is if you want to do some advanced interactivity. That can sometimes be easier in SVG.

I'd be happy to review any PR to improve our rollup & package.json config as long as it's backwards compatible with the documented methods of using Chart.js: https://www.chartjs.org/docs/latest/getting-started/integrat...

There have been two major changes in Chart.js that will dramatically improve performance in the upcoming 2.9.0 release. We're also adding a section to the documentation about options you can set to improve performance over the defaults. We're hoping to release soon, but there are a couple pending PRs we'd like to review first

Also, if you're interested in realtime charts, here's a related plugin I've seen: https://github.com/nagix/chartjs-plugin-streaming