Video shows them opening the hackaday website and pressing “accept all” on the “share and sell personal data with and to third parties” dialog. 🙈
Just gotta close it off on both ends<===>
(parens for round ends didn't look good)
I don't get what your bridge example is supposed to show, nor what normalizing substandard practice has to do with politics or lack thereof.
Depending on where you look there's plenty of shoddy construction work and cutting corners for cost, big projects are notorious for taking longer and costing more in the end. Construction had more time to develop and be regulated, and has more physical limitations compared to software development. Both, in the end, can be (theoretically) held accountable before court.
is to be able to communicate this effectively with management
Isn't this politics? Why are you saying politics has no place in engineering principles?
Software engineers are much more replaceable than construction engineers/architects, both in-discipline and with less expertise.
I do my part in what I can influence and control, delivering good and sound products, but it's obvious depending on individuality doesn't work across our whole industry.
/edit: The linked article talks about how in-company politics are necessary to coordinate and deliver features. I don't see that addressed here either? How would you deliver - taking the example from the article - Latex in Markdown on GitHub without politics?
And link to the project homepage, not the release note. Or maybe both.
Did you open the link? The release notes have a project description, not just a change log.
I worked on and created a lot of things, but when thinking 'cool', the fractal rendering I did a long time ago popped into my mind as well. It just looks cool, interesting, has variance and experimentation, and is very visual.
This proposal is an early design sketch by Blink Layout Team in Google to describe the problem below and solicit feedback on the proposed solution. It has not been approved to ship in Chrome.
linked src
Great, I'm glad it helps. Good luck! :)
I wonder if we can do even simpler today (with a framework that handles the dynamic aspects of the application, not with barebones JS).
You want a stateful application or a template-model-rendering system?
If not, the webbrowsers support fetch API and you can create HTML from that, or set values on the DOM elements.
Personally, I'm not too familiar with JS frontends in particular. I could name some random names, but don't have experience or particular opinions. What I've read, and intuitively agree with, is that many of the most popular frameworks introduce additional complexities and their own state system when the browser nowadays would cover those natively. Newer frameworks that make use of the current browser tech may be better. But I can't name specific names.
I myself, in terms of web frontend frameworks, work with Blazor (dotnet). Upside being direct C#/dotnet integration and development and wide options, downside being the tech complexity of framework between browser and backend and a mixing of HTML and Razor concerns.
If it were me, I would probably create an .html file, add a <script> block, and use the fetch API to fetch the data from the backend and then render/display it via JS/HTML. It's always possible to size up and add complexity later.
Six months ago, distributed crawling hit code.forgejo.org, and the mitigation measures put in place then held until a few weeks ago. The mitigation measures relied on JavaScript-based proof-of-work, but the crawling software learned to resolve the measures, allowing the attack to return.
Since November 24, a new blocking strategy has been implemented and successfully blocked around one million unique IPs daily. Only 5,000 unique IP addresses reach code.forgejo.org daily, and no reports of legitimate traffic being blocked have been received.
Crazy. A 1M to 5k ratio.
The linked to 'new strategy' information is interesting too. They're blocking a specific user agent.
TL;DR: 26 November ~900,000 unique IPs sent requests to code.forgejo.org and blocking one user agent effectively blocks over 90% of them. At the moment ~50,000 unique IP hit code.forgejo.org per hour, ~5,000 of them are not using the suspicious user agent and are sent to Anubis, ~1,000 of them pass the challenge and reach code.forgejo.org.
&& Header(`user-agent`, `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36`)
Typically, I could have a program I wrote doing stuff, I may add a little HTTP server feature to it as an entrypoint to its internal and then have a cute webapp to connect to it to visualize what is going on, idk.
Are you saying you could add HTTP endpoints to your services which can then be queried for data? So REST APIs for example?
Do you want live updates on the UI or is a fetch visualization enough?
For simple fetch visualization, creating a simple web app with browser native JavaScript and HTML seems like a fine, simple solution for barebone/hacky visualizations.
If you want live updates, there's a few alternatives. Polling from REST API, long-running streamed responses (http server sent events), or Websocket (continuous connection and communication). Websocket will need the capability on the backend server.
If you're imagining a reporting/monitoring like tool/UI, using OpenTelemetry and one of many existing collect and store and display solutions could be relatively simple setup, with a bit more investment into serving OpenTelemetry data.
There's various technologies and frameworks. You could choose any one, or choose one closer to your tech stack, whatever you use.
The author provided no evidence of it
They're contextualizing and sourcing it plenty. It's their impression from their experience, from their years of being in that field. In the later adding of comments at the end they go into different takes as well, reiterating that it's what they saw or see in [their] big corp[s] [and those he talks to].
You're saying people are rotating too often - which was one of their points. Not sure if you meant support that point or point it out [assuming they didn't].
Sharing, because I had to look up Abstract Wikipedia
Abstract Wikipedia is an in-development project of the Wikimedia Foundation. It aims to use Wikifunctions to create a language-independent version of Wikipedia using its structured data.