demesisx
Now
•
100%
Sounds great! Thanks for looking into that. I’m a bit of a jack of all trades. So, I tend to try and thoroughly vet a technology before I really dive in and commit my blood, sweat, and tears.
A couple of weeks ago, I found a previous implementation in Haskell. If I were really approaching the stack that I think will be best for the future, perhaps I should fork that one. I’m wishing Purescript was ready for prime time (was popular enough to have more educational material) because that would be a no brainer…especially the work they’ve recently been doing with a Chez Scheme back end.
I’ll start to look into it more in the coming week. Thank you so much! I have a community setup for this idea at https://infosec.pub/c/Lemventory
I may change it, though, since this is no longer Lemmy-related. As I realized, inventory is just not suited to Pub/Sub due to the need to have varying levels of security for the information being broadcast and subscribed to.
demesisx
Now
•
100%
I’m a fan of crypto but I happen to hold the strong opinion that BTC’s authentication algorithm shouldn’t have been chosen because it’s not secure enough for future proofing. Furthermore, that BTC tie-in will alienate many people including myself. Anyway, I’d love some help forking NOSTR to NOT use BTC authentication because that task is FAR beyond my skills.
demesisx
Now
•
100%
Perhaps I’m the one who’s mistaken.
I came to this conclusion because: From my initial cursory investigation of NOSTR, in all of the instructions to get started I found, the first step was to create a lightning wallet. Maybe I’m incorrect but, from what I understood, BTC’s authentication is one and the same with NOSTR’s authentication.
demesisx
Now
•
100%
Edited. Good call.
demesisx
Now
•
100%
If you want to have a go at using that NOSTR tech but stripping the lightning wallet thing out for another (less BTC maximalist but equally or even more secure) form of authentication, I’d be very interested. I’m obviously not going to roll my own auth from scratch….but as I see it, tying BTC to it could prevent MANY people from giving an otherwise very promising tech a chance. Besides, there are already far more secure cryptographic elliptical curves in use by other cryptocurrencies that NOSTR conspicuously passed over in favor of BTC’s.
I probably don’t have the resources nor experience to do it myself but I’d love for this tech to exist.
demesisx
Now
•
100%
If you find that the fediverse isnt the right tech for this kind of thing, have a look at NOSTR. I recently learned about it in the context of my hypothetical Lemmy fork. For what I am trying to do with it (decentralized retail inventory), NOSTR was much better suited than Lemmy. My only issue with it is that it ties bitcoin lightning walllets into its authentication mechanism (a dealbreaker for me at least). My future uses for it would be FAR different than yours but it also seems more well-suited to activism as well.
demesisx
Now
•
100%
I got you, fam(ily). It has a real smooth, simple ring to it. ;)
demesisx
Now
•
97%
Temu: contribute to the irreversible heat death of your own planet just to save some money on useless, piss poor quality trinkets created out of cancer-causing, hazardous materials using slave labor coupled with unfair market practices that are then shipped thousands of miles over the oceans using the world's worst polluting container ships.... like a billionaire.
That should be their slogan.
edit: added slave labor, unfair market practices edit: added hazmat
demesisx
Now
•
100%
Judging by the state of the US, you're much more likely to be right than I am, you cynical bastard!
😂
demesisx
Now
•
100%
I think I would just need one. We'd have to work in opposing shifts to get my billion Euro idea out the door in a more reasonable time frame than the one I have currently been working in.
demesisx
Now
•
100%
🤣
demesisx
Now
•
100%
Trains are awesome and I fully support them but let's not be idealistic here and pretend that true self driving cars will never happen.
Edit: jokes on you! I made a grammatical correction that makes your reply IRRELEVANT. 😉
demesisx
Now
•
95%
SELF-DRIVING TECHNOLOGY SHOULD BE STANDARDIZED AND OPEN SOURCE.
Any other implementation puts profits over human lives.
demesisx
Now
•
75%
demesisx
Now
•
100%
In my case, whether I’m wrong or not, they actively discourage me from using my brain.
demesisx
Now
•
75%
I'm an intellectually overqualified filmmaker surrounded by anti-intellectuals (I routinely get made fun of for being interested in technical stuff)....and right now, I am on workman's comp with a broken foot. So: exactly what I am doing right now is exactly what I would want to be doing.
What's that?
Hanging out with my daughter in my lab,
Learning
- Haskell/Plutus
- Purescript
- using Nix to glue them together
- hacking an espresso machine (either with a RISC_V Lychee Pi or an ESP32...haven't decided yet).
Practicing:
- guitar
Blazing:
- chronic
youtu.be
> Answering the question raised at the end of Part 1, we take a look at how a hypothetical Strict Haskell would tie the compilers hands despite pervasive purity. We also examine how laziness permits optimizations that come with no intrinsic cost and compare its benefits to a strict language with opt-in laziness. > > Part 1: > > • Laziness in Haskell — Part 1: Prologue > Series Playlist: > > • Laziness in Haskell > > — > Contact: > • Tweag Website: https://www.tweag.io/ > • Tweag Twitter: https://twitter.com/tweagio > • Alexis King's Twitter: https://twitter.com/lexi_lambda
> In the second webinar from our Hackathon series, Fabian Bormann provides an intro into building on Cardano including a list of tools to support you. Next, Mateusz Czeladka discusses how to harness the power of smart contracts with Aiken. > > Click the link below to learn more and to register for the Cardano Summit Hackathon. > https://summit.cardano.org/hackathon/
demesisx
Now
•
75%
That’s a bummer. David Portnoy is alt-right.
demesisx
Now
•
100%
The Finest Possible Caprese Sandwich:
- fresh Baked Stirato Italian Baguette
- fresh Mozzarella di bufala
- fresh-picked Heirloom Italian Genovese Basil
- fresh-picked San Marzano Tomatoes
- Frantoia 100% Italian Extra Virgin Olive Oil
- Mediterranean Sea Salt
- Giuseppe Giusti Premio Italian Balsamic Vinegar
demesisx
Now
•
100%
I'm finding the signal to noise ratio is higher here. Much higher quality content at the moment. I even see some bots that post the entire article rather than just linking it. I hope that catches on.
demesisx
Now
•
100%
In my experience, Voyager is still pretty buggy too. For example, try editing a post then go to do anything else after the fact. I always have to restart the whole app when I go to edit a post I made. They have a ton more features than anyone else but there are still tons of bugs.
react native is another layer and lags behind the dev of swift by at least a year. This is a huge problem for new api's like SwiftUI, in my experience. Ps. Native is ALWAYS better than an approximation of native.
cross-posted from: https://programming.dev/post/719255 > **Back Cover Text** > > The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. > > ***Domain-Driven Design*** fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development. > > Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis—refactoring not just the code but the model underlying the code—in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. ***Domain-Driven Design*** then builds on this foundation, and addresses modeling and design for complex systems and larger organizations. > > Specific topics covered include: > > - Getting all team members to speak the same language > - Connecting model and implementation more deeply > - Sharpening key distinctions in a model > - Managing the lifecycle of a domain object > - Writing domain code that is safe to combine in elaborate ways > - Making complex code obvious and predictable > - Formulating a domain vision statement > - Distilling the core of a complex domain > - Digging out implicit concepts needed in the model > - Applying analysis patterns > - Relating design patterns to the model > - Maintaining model integrity in a large system > - Dealing with coexisting models on the same project > - Organizing systems with large-scale structures > - Recognizing and responding to modeling breakthroughs > > With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations. >
youtu.be
> "So the rotary fixture plate is done, right? WRONG. I’ve got just one more feature to add to it. A set of material squaring guides. I have an idea for a dovetail clamp that allows for adjustability, but is also self-squaring. I’ve never seen anything quite like it which could either be a good thing or a bad thing. It’s one of those weird things where the mechanism makes sense, but at the same time… doesn’t. So let’s find out, and build a functional prototype!"
I listen to this (now very old) episode often to get inspired. When John starts talking about compiling to categories, at around 14:40 to around 30:00, it gets REALLY interesting. *😁😁 Hoping to bring this kind of discussion to the new Formal Methods community. 😁😁 * Here's the work he talked about: [Compiling to categories by Conal Elliott](http://conal.net/papers/compiling-to-categories/) I need someone to get into the weeds on compiling programs to "axiomatized closed categories". What are the implications? What are the ramifications?
corecursive.com
Here's the conclusion of the paper Wadler is referring to in this interview: > Proposition as Types informs our view of the universality of certain programming languages. The Pioneer spaceship contains a plaque designed to communicate with aliens, if any should ever intercept it. They may find some parts of it easier to interpret than others. A radial diagram shows the distance of fourteen pulsars and the centre of the galaxy from Sol. Aliens are likely to determine that the length of each line is proportional to the distances to each body. Another diagram shows humans in front of a silhouette of Pioneer. If Star Trek gives an accurate conception of alien species, they may respond “They look just like us, except they lack pubic hair.” However, if the aliens’s perceptual system differs greatly from our own, they may be unable to decipher these squiggles. What would happen if we tried to communicate with aliens by transmitting a computer program? In the movie Independence Day, the heroes destroy the invading alien mother ship by infecting it with a computer virus. Close inspection of the transmitted program shows it contains curly braces—it is written in a dialect of C! It is unlikely that alien species would program in C, and unclear that aliens could decipher a program written in C if presented with one. What about lambda calculus? Propositions as Types tell us that lambda calculus is isomorphic to natural deduction. It seems difficult to conceive of alien beings that do not know the fundamentals of logic, and we might expect the problem of deciphering a program written in lambda calculus to be closer to the problem of understanding the radial diagram of pulsars than that of understanding the image of a man and a woman on the Pioneer plaque. We might be tempted to conclude that lambda calculus is universal, but first let’s ponder the suitability of the word ‘universal’. These days the multiple worlds interpretation of quantum physics is widely accepted. Scientists imagine that in different universes one might encounter different fundamental constants, such as the strength of gravity or the Planck constant. But easy as it may be to imagine a universe where gravity differs, it is difficult to conceive of a universe where fundamental rules of logic fail to apply. Natural deduction, and hence lambda calculus, should not only be known by aliens throughout our universe, but also throughout others. So we may conclude it would be a mistake to characterise lambda calculus as a universal language, because calling it universal would be too limiting.
[sleet](https://github.com/snowfallorg/sleet)
share.transistor.fm
A podcast [with transcript](https://spectrum.ieee.org/functional-programming-biggest-change) which may help explain fp to laymen.
youtu.be
A great talk by one of the greats to get the ball rolling in this new community.
I was looking into the prospect of deploying an instance of Lemmy myself. Being an ULTRA nix fanboi (and a Docker-hater), I was immediately struck by how much the process still depends on (and, IMO, is being held hostage by) Docker containers. Can we (or at least someone more capable and with more free time than I) help the Lemmy community by harnessing the power of nix and flakes to create declarative, reproducible Lemmy scratch-built instance deployment? I suspect it would be exceptionally easy for some of you out there. If you are a flakes power-user, just think of how much this could help the community (and perhaps awaken a few people to the power of flakes). ps. if this already exists, please point me in the right direction.
Now
demesisx
programming.devPlutus, Haskell, Nix, Purescript, Swift/Kotlin. laser-focused on FP: formality, purity, and totality; repulsed by pragmatic, unsafe, "move fast and break things" approaches
AC24 1DE5 AE92 3B37 E584 02BA AAF9 795E 393B 4DA0