Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categories
  3. Uncategorized
  4. Inizio oggi una nuova avventura: da Java in Processing-IDE a C++ in ambiente OpenFramework.

Inizio oggi una nuova avventura: da Java in Processing-IDE a C++ in ambiente OpenFramework.

Uncategorized
4 2 0
Log in to reply

Feed RSS
Inizio oggi una nuova avventura: da Java in Processing-IDE a C++ in ambiente OpenFramework.

Gli ultimi otto messaggi ricevuti dalla Federazione
  • Joe Cooper 🇺🇦 🍉undefined
    Joe Cooper 🇺🇦 🍉

    @kkarhan I mean, that's what inflation means. Buying power of USD declines, prices go up.

    read more
  • Kevin Karhan :verified:undefined
    Kevin Karhan :verified:

    @swelljoe nah, the is loosing value.

    Like serioisly…
    read more
  • Joe Cooper 🇺🇦 🍉undefined
    Joe Cooper 🇺🇦 🍉

    Inflation has gone nuts. Just paid twenty bucks for one entree from a Chinese place. Nothing fancy, and while I've never been to this particular place and the food was quite good, I would have expected vegetable delight with tofu to be about ten to twelve bucks.

    I don't want to be an old man with an onion tied to my belt, but, really, everything has gotten remarkably more expensive in such a short time.

    read more
  • Antonella Ferrariundefined
    Antonella Ferrari
    Manifestazione per la libertà di stampa a Roma, ovazione per Ranucci


    @giornalismo
    articolo21.org/2025/10/manifes…
    Ovazione per Sigfrido Ranucci e la redazione di ‘Report‘. Il giornalista Rai, vittima di un attentato, è salito sul palco della manifestazione per la libertà di

    read more
  • Poliverso - notizie dal Fediverso ⁂undefined
    Poliverso - notizie dal Fediverso ⁂
    @scottjenson I completely agree. I always try to make it clear to users of my forums that they shouldn't object to the way other users post.
    Users can report any rule violations to us moderators either through the integrated reporting system or by direct message. If they don't receive a satisfactory response, they can mute or block that user. But they shouldn't harass other users, otherwise the social Fediverse will be under such pressure that only the troublemakers will remain.
    read more
  • mayohnyoundefined
    mayohnyo

    Hey folks,

    If you have the opportunity, I would kindly suggest to move off of mastodon.social.

    It's one of the biggest, if not still the biggest instance and has been showing problematic activity not just now, but over the years.

    That means being blocked by that instance, or trying to block that instance results in losing contact with a lot of people.

    Which happened to @fabio just recently for the second time by being blocked. And I don't think any other instance to speak of did that.

    The NPO behind it is also registered in Germany.

    - a country which has the "Staatsräson" since 2008 of "The security of Israel is unnegotiable", "Our unconditional solidarity with Israel has never been under question for me. My personal relationship with Israel is unconditionally good." (then chancellor Angela Merkel)

    Of course not a word about the security of Palestine or Palestinians.

    - The country where now the Chancellor echoed words and the sentiment of former Nazi head propagandist Goebbels, by talking of migrants as an issue for the city image, for which he does not apologize. He also does not admit to a genocide being committed by Israel, even when Human Rights Watch, Amnesty International, the UN and genocide experts have identified and declared it as such.

    - A country where a recent study of hundreds of TV and Newspaper reports for 2025 has shown that 95% of criminal suspects they reported on were foreigners, even though they only make up 34.3% of the actual criminal suspects.

    Germany is deeply racist and pro-Israel.

    - There was a strong push, which I did not follow of how successful it was, of defining antisemitism to put under suspicion of it any criticism of Israel, and stopping public funding for organisations that do not adhere to that definition.

    I think it's naive to think that all this does not also put pressure on an influential project of public opinion such as mastodon.social.

    https://www.volksverpetzer.de/analyse/studie-groesste-taetergruppe-systematisch-verschwiegen/

    https://de.wikipedia.org/wiki/Staatsr%C3%A4son

    https://www.bpb.de/shop/zeitschriften/apuz/antisemitismus-2024/549358/israel-und-der-antisemitismus/

    https://www.tagesschau.de/inland/innenpolitik/deutschland-israel-staatsraeson-100.html

    read more
  • liberoundefined
    libero

    @mzll
    Non ti montare la testa 😁😁
    Penso che basta rallentare e cercare più a fondo e si incontra bella gente .

    read more
  • Evan Prodromouundefined
    Evan Prodromou

    If you're on a social media platform that's not on the Fediverse yet, TELL THEM.

    read more
@pierobosio@soc.bosio.info
Post suggeriti
  • lotus root soupundefined

    More old art from 2023.

    Uncategorized mastoart digitalart art tootsea firealpaca fediart
    1
    1
    0 Votes
    1 Posts
    0 Views
    lotus root soupundefined
    More old art from 2023. This was a piece I made to express my feelings after leaving a toxic online friendship I had. She made me feel like I couldn't leave, but that I was the abusive one whose hurt was paranoid and unfounded.Inspired by wayang kulit.#mastoart #digitalart #art #tootSEA #firealpaca #fediart
  • Davy Jonesundefined

    Which software design principles do you rely on most?

    Uncategorized programming
    3
    0 Votes
    3 Posts
    2 Views
    Davy Jonesundefined
    Summary of A Philosophy of Software Design by John Ousterhout Source: danlebrero.com These are notes by Daniel Lebrero Berna on John Ousterhout’s A Philosophy of Software Design. Some advice in the book goes against the current software dogma. The current dogma is the result of previous pains, but has now been taken to the extreme, causing new pains. What the author solves with “Comment-First Development,” others solve with Test-Driven Development. The excuses for not writing comments mirror those for not writing tests. Key Insights It’s easier to see design problems in someone else’s code than your own. Total complexity = Σ(complexity of part × time spent on that part). Goal of good design: make the system obvious. Complexity accumulates incrementally, making it hard to remove. Adopt a “zero tolerance” philosophy. Better modules: interface much simpler than implementation (Deep modules). Design modules around required knowledge, not task order. Adjacent layers with similar abstractions are a red flag. Prioritize simple interfaces over simple implementations. Each method should do one thing and do it completely. Long methods are fine if the signature is simple and the code easy to read. Difficulty naming a method may indicate unclear design. Comments should add precision or intuition. If you aren’t improving the design when changing code, you’re probably making it worse. Comments belong in the code, not commit logs. Poor designers spend most of their time chasing bugs in brittle code. Preface The most fundamental problem in computer science is problem decomposition. The book is an opinion piece. The goal: reduce complexity. 1. Introduction (It’s All About Complexity) Fight complexity by simplifying and encapsulating it in modules. Software design is never finished. Design flaws are easier to see in others’ code. 2. The Nature of Complexity Complexity = what makes code hard to understand or modify. Total complexity depends on time spent in each part. Complexity is more obvious to readers than writers. Symptoms: change amplification, cognitive load, unknown unknowns. Causes: dependencies, obscurity. Complexity accumulates incrementally; remove it aggressively. 3. Working Code Isn’t Enough Distinguish tactical (short-term) from strategic (long-term) programming. The “tactical tornado” writes lots of code fast but increases complexity. 4. Modules Should Be Deep A module = interface + implementation. Deep modules have simple interfaces, complex implementations. Interface = what clients must know (formal + informal). Avoid “classitis”: too many small classes increase system complexity. Interfaces should make the common case simple. 5. Information Hiding (and Leakage) Information hiding is key to deep modules. Avoid temporal decomposition (ordering-based design). Larger classes can improve information hiding. 6. General-Purpose Modules Are Deeper Make modules somewhat general-purpose. Implementation fits current needs; interface supports future reuse. Questions to balance generality: What is the simplest interface covering current needs? How many times will it be used? Is the API simple for current use? If not, it’s too general. 7. Different Layer, Different Abstraction Adjacent layers with similar abstractions are a red flag. Pass-through methods and variables add no value. Fix pass-throughs by grouping related data or using shared/context objects. 8. Pull Complexity Downwards Prefer simple interfaces over simple implementations. Push complexity into lower layers. Avoid configuration parameters; compute reasonable defaults automatically. 9. Better Together or Better Apart? Combine elements when they: Share information. Are used together. Overlap conceptually. Simplify interfaces or eliminate duplication. Developers often split methods too much. Methods can be long if they are cohesive and clear. Red flag: one component requires understanding another’s implementation. 10. Define Errors Out of Existence Exception handling increases complexity. Reduce exception points by: Designing APIs that eliminate exceptional cases. Handling exceptions at low levels. Aggregating exceptions into a common type. Crashing when appropriate. 11. Design It Twice Explore at least two radically different designs before choosing. 12. Why Write Comments? The Four Excuses Writing comments improves design and can be enjoyable. Excuses: “Good code is self-documenting.” False. “No time to write comments.” It’s an investment. “Comments get outdated.” Update them. “Comments are worthless.” Learn to write better ones. 13. Comments Should Describe Things That Aren’t Obvious Comments should add precision and intuition. Document both interface and implementation. 14. Choosing Names Names should be precise and consistent. If naming is hard, the design likely isn’t clean. 15. Write the Comment First Like TDD, comment-first helps design, pacing, and clarity. 16. Modifying Existing Code Always improve design when changing code. Comments belong in code, not commit logs. 17. Consistency Don’t “improve” existing conventions without strong reason. 19. Software Trends Agile and TDD often promote tactical programming. 20. Designing for Performance Simpler code tends to be faster. Design around the critical path. 21. Conclusion Poor designers spend their time debugging brittle systems.
  • Mystic ☁️✨undefined

    Time for a new #introduction over here!!Hello everyone, I'm Mystic!

    Uncategorized introduction digitalart mastoart illustration イラスト
    1
    4
    0 Votes
    1 Posts
    3 Views
    Mystic ☁️✨undefined
    Time for a new #introduction over here!!Hello everyone, I'm Mystic! I'm an Artist and Vtuber (tho i mainly just share my art over here) with a passion for my OCs, Cute girls, and Elves ✨I also watch a fuck ton of anime and will gladly yap about the silly little guys that live in my head at a moments noticeComm Info: https://mysdriel.uwu.aiStreams: https://www.twitch.tv/mysdriel#DigitalArt #MastoArt #Illustration #イラスト
  • Jan Schaumannundefined

    It's that time of year again!

    Uncategorized programming unix apue
    40
    0 Votes
    40 Posts
    0 Views
    Jan Schaumannundefined
    Advanced Programming in the Unix EnvironmentTool Tip: ed(1) is the standard text editorAs part of our discussion of unix development tools, we take a short detour to provide a quick walkthrough of ed(1), the standard text editor. This is not done merely to up your geek creds, but understanding ed(1) will also helps us better understand other tools like vi(1), sed(1), and ultimately even things like diff(1) and patch(1) better.https://youtu.be/mRZsV7aMK0I#apue #unix #programming #ed