Hacker Newsnew | past | comments | ask | show | jobs | submit | HendrikR's commentslogin

I work on a team building a real-time display of energy flows (production and consumption) on a regional basis (by municipalities). This is mainly used in town halls on a flat-screen display but of course publicly accessible as well. It‘s made with VueJS but will be rewritten with Svelte very soon. Here‘s one example of one of over 140 municipalities at the time of this writing:

https://energiemonitor.bayernwerk.de/abensberg


How exciting this would be to cycle through the tunnel once the tunnel is completed but not yet released to public (car) traffic? Near Hamburg people enjoy riding their bikes on a nearly completed section of a new motorway although it's strictly forbidden.


On a sidenote: If you would like to read this article without giving away your email address or signing in, activate the 'Reader' option in your browser.


Or disable JavaScript.


Or install the bypass news paywalls extension. https://github.com/iamadamdev?tab=repositories


Or go to your local newsstand, pick up a copy, and leave without paying for it.


… and people would look into https://svelte.dev which might be everything you need.


They don't have enough funding. Next.js and Gatsby are in an entirely different weight class compared to Sapper.

https://sapper.svelte.dev/


And... Sapper is dead btw.

Rich said it recently in a video. The Svelte team is working on the next big thing combining Svelte with Snowpack. The project is called SvelteKit.

https://www.youtube.com/watch?v=qSfdtmcZ4d0


I think retiring Sapper was the right decision. I have a feeling Rollup will meet a similar end too.

They both seemed like fine pieces of software. They just don't seem offer separate much their counterparts nowadays that warrants continued feature development.


Rollup isn't going anywhere! When you poke behind the scenes of newer build tools, like Snowpack and Vite and the custom compiler that powers Remix Run, you'll find Rollup doing a lot of the heavy lifting. And it's the preferred choice of most libraries. There's a reason for that :)


Thanks for the correction, Rich.

I just watched your presentation at Svelte Summit and I'm looking forward to how Svelte progresses.


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


SvelteKit will replace Sapper which will never reach 1.0. Development on Sapper will stop (or probably has already stopped).


Maybe this can save someone some confusion: When I searched the first result for SvelteKit seems to be another project that is dead.


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


Should be called SveltePack IMO :)


Or even better, Vue.js

I am not sure I buy into all the svelte hype, and even if claims about it's speed/build size are true - the difference isn't enough to outweigh the enormous advantage vue has in terms of a more mature ecosystem/tooling.


Most remarkable: "The bulb that still worked after 70 years" - "A light switch - probably installed in the 1950s - illuminated a large Osram bulb marked 'HM Government Property'."


Yes there is a lightbulb conspiracy among producers that deliberately and jointly shortened the life span of their products in order to ramp up sales.


There's some truth to the fact that lightbulbs don't last as long as they used to; but there's a lot to unpick here.

First: This bulb was not turned on, and a light-bulb in storage does not degrade, there's no oxidisation happening inside the bulb itself.

Second: heavy filaments consume more power to emit light, and a heavy filament is the requirement to have a long-lived bulb

Third: Even with a heavy filament, bulbs will dim in their light output with years of use. The longest running light bulb in the world (101 powered on years if I'm not mistaken) is less bright than a candle, although originally it was about as bright as a 40w bulb.

More information on that bulb: https://en.wikipedia.org/wiki/Centennial_Light


> and a light-bulb in storage does not degrade

Depends on the quality of the seal and how well it was evacuated. Older bulbs tend to be higher quality, thicker glass, much more material around the seal (the spot where the wires cross through from inside the bulb to outside).


Also I imagine these bulbs from the 50s were more expensive than today's bulbs, no?


Are you thinking of the Phoebus Cartel?

https://en.m.wikipedia.org/wiki/Phoebus_cartel

I suppose it's accurate to call it a conspiracy since they literally conspired to divvy up markets and set predetermined bulb lifetimes.


For those downvoting me, here is the link to the trailer of the documentary of this 'planned obsolescence' conspiracy of the producers: https://www.youtube.com/watch?v=8KSC84K4rcY


Just an note, the article got the text wrong here.

The bulb actually reads: "Property of H.M. Government."


A comparable behaviour can be seen for years now on iOS. Chrome for iOS is advertised where possible, even if you would like to open a hyperlink from the show notes of a YouTube movie: You are offered to open this link with Chrome ("download"), Google App ("download"), or even with Safari ("open"). There's no real use for the user having Chrome on iOS as long as it has to use WebKit as a rendering engine, the same engine Safari uses. But there is surely a usage for Google, monetizing the user's browsing profiles.


Safari just joined the party in displaying a warning if the connection is not using TLS/HTTPS just like other browsers do.


From their announcement:

We are announcing today that the Copy and CudaDrive services will be discontinued on May 1, 2016.

Copy and CudaDrive have provided easy-to-use cloud file services and sharing functionality to millions of users the past 4+ years. However, as our business focus has shifted, we had to make the difficult decision to discontinue the Copy and CudaDrive services and allocate those resources elsewhere. For more information on this decision, please view the blog post from Rod Mathews, our GM of Storage.

We know this comes as disappointing news to our users, but rest assured that we will do everything we can to take care of each of you in the manner for which Barracuda is known. We have created a step by step guide that walks you through the process of moving your data to a local hard drive or another cloud storage solution.

If you are on a paid subscription for either Copy or CudaDrive, please keep an eye out in the coming days for an email with more detailed information on your options. For additional information, please visit our FAQ page.

Thank you to everyone for your support.

All the best,

The Copy & CudaDrive Team


You can have a look at WordFence as well which comes free of charge (and there are paid plans). It does checksumming and guards your login page. https://www.wordfence.com


This is really awesome. Why do certificates expire in the first place?


By having an expiry, revoked certs can be forgotten about once the expiry has passed. We'd need to keep a forever growing list of revocations otherwise.


Also certs get switched to ones with stronger algorithms and longer keylengths after expiry. You also would have to revoke old certs all the time when their crypto isn't safe anymore.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: