bitfucker @ bitfucker @programming.dev

Posts

1

Comments

425

Joined

1 yr. ago

Well, how would you measure C directly? You can only always get 2C.

I think a lot of people here read the headine and think OpenSSL is moving everything to github and giving up everything else. It is not. They only moved the means of distributing the release tarball to github and stopped supporting the ftp and rsync. Do not confuse distribution and contribution/development.

You are mistaking contributing and distributing.

Edit to clarify: The blog is strictly speaking about the means of distributing the release tarball. Distributing the release tarball has nothing to do with how contribution is accepted or how issue is handled. What they say on the blog is also very clear IMHO and for a good reason. Maintaining infrastructure takes work. Works that if you didn't do it right can be an attack vector. Do you guys remember xz? Do you read how the vulnerabilities came to be? Maintaining a single source of truth for the release tarball can help mitigate that. If one malicious actor can control even one of the distribution channels of the release tarball we get xz 2 electric boogaloo.

And this is how we got everything must be online/subscription or everything is a web app. And people complain about that too.

I think the 1% is so that a company didn't shy away from open source completely. I don't know how it will work for example if the company is using 5 of this license. Will they pay 5% or 1%? Probably 1%, but I didn't see it addressed in the article. Anyway, since the cost is small for a big company, but can be huge in number for an individual, I think it is fair.

Also, what if a contributor is acting on behalf of a company? Would the company receive the payment or the individual contributor? There is just so much to cover.

Understandable actually. Server maintenance costs money and if a 3rd party chat app; which significantly has more usage than other forms of social media; is trying to connect to the server, they have to handle that traffic too. Remember, it is not just about data size, but also the sheer volume of connection to handle.

I think the solution is just P2P with each peer acting as a relay to the other too. The protocol needs to be designed in such a way that no-one in the middle can reply to send false acknowledgement so as to prevent sybil attack or other attack where a malicious actor is a part of the network.

Size wise, it is small relative to the ship size. Look at car engine. How many % of volume is taken up for the engine and fuel tank of car? I think it is close to 30-40%

Until you realize that the energy requirement is also different. Land transport in general is very inefficient. Ship is in fact one of the most energy efficient means of transport.

So to compensate for a poor service that is epic game launcher you have to turn to oss solution maintained by the community thanklessly while still giving epic the 25% cut of your sale? I'd rather not give epic any money at all

Yeah, sometimes computer can act normal (boot and everything) but the system has somehow become unstable. Sometimes that means there is improper hardware installation, or in embedded system, something is nearing its end of life due to defect or other myriad of factor.

I didn't follow the saga but, have you tried reflashing the firmware and reinstalling klipper? Also, where did you run klipper from? Did you have a spare sbc to test on? Some incorrect software behaviour could also be a result of hardware failure or malfunction that wasn't really visible.

Did you died tho?

Mao

Where is the "legacy system needs to be maintained, salary goes up"? But yeah, it's a pretty good picture of the tech landscape

Technically there is. If the device uses BLE or the phone has some built in hardware shenanigans. There is also a local gateway via ble. I'd argue a simple gateway is not a "server". Scheduling can be done by the device via internal non-volatile storage and RTC

Tell Empress to chill

Uhhhmmmm

Oh man, can't wait to post a full book of the lord of the rings as a facebook post and make it legal for facebook to use it as training data. Words can absolutely be copyrighted/licensed, otherwise books and scientific journal copyright/license is BS too. Big company however, usually has EULA that states you as a user grant the company the right to basically do whatever the fuck they want to do with your content. As much as I'd like that to be a reality especially for millions of research paper, but the current reality is that copyright law sucks ass.

Why not try flutter then?

Client still needs to call the server. How offline PWAs work then? They emulate server in ServiceWorkers.

Yes they do need server for initial resource loading. Usually with PWA, you need to fetch the static resource once from a CDN since every resource is bundled. And no, they don't need to emulate server in service worker, wtf. You can if you want, but you can also store the data locally using indexeddb and sync periodically baked into the app. Service worker doesn't emulate server, they just intercept a network call and check their cache. A man in the middle if you will. I think it is debatable if that is called emulating a server or not.

1. Let's call it page generation to not confuse with actual rendering.

Yeah, that is fair. Its just the usual web tech shenanigans.

2. It not always saves bandwidth and processing time, but static resources can allow to hide CDN latency on initial load. Although it is not property of SPAs, just separation of static and dynamic part and generating dynamic part after static page already shows something.

When developing an application, you usually didn't develop the dynamic and static part separately. Which data can be cached and which needs to be sent to the origin so it can be properly generated. If you fail to configure it correctly the static resource which should go to a CDN get sent to your origin instead. With SPA you just ship the frontend to the cdn and make the backend separately.

3. It will still result in more requests, but may trasfer less data per request. May.

I mean, if you are making an SPA without splitting the bundle, there should only be a single html, css, and js. A bunch of images and some font too if you want to be complete. But if you are making the page server generated, you always need to transmit the HTML. ALWAYS. So I think it definitely saves requests.

Static web page after loading will not request more styles. SPAs imply client-side dynamic page, and they may request more data INCLUDING styles. Also client still need to load styles on page load.

SPA will not request more style if you are bundling them tho? Wtf are you talking about? Unless you explicitly split the style, once SPA is loaded every page navigation is just JavaScript replacing the whole HTML with the one bundled in the JS file.

Write for QT.

Sure, QT exist as a UI library for cross platform. But that doesn't solve the iOS mafia. We only got Apple to allow 3rd party store now, we haven't got sideloading yet. It is a hassle if you want to make an app that can be used in any devices. Especially if the app is just some form filling app.