418 karma · joined September 25, 2014
the refill costs more than the original pen
people have been misusing the term cybernetic for a while now, I've noticed...
people have been misusing the term cybernetic for a while now, I've noticed...
I'm also skeptical of the graph on your front page that claims S3 cost as much as DynamoDB.
that alone makes it look like total nonsense.
as someone else said, extraordinary claims require extraordinary evidence.
perverse incentives indeed.
It operates over the 900 megahertz ISM band. I'm able to walk all over my house and property without audio dropping out, and it doesn't suffer from Bluetooth codec compression issues.
https://www.eposaudio.com/en/us/headsets/dect-headsets
I will say they suck for listening to music though (if you're an audiophile)... but I would just switch to good studio monitors for that situation.
it's pretty classic... you have the same problem with other architectures too, whether it's a monolith, event driven, SOA, distributed monolith, etc... bad design and ill defined dependencies have literally nothing to do with micro services anymore than any other architecture.
blaming some specific architecture pattern for bad design is silly. bad design is bad design. lack of the ability to evolve a system over time is bad design, it has nothing to do with the architecture necessarily.
that being said, I do generally dislike microservices personally, for large complex systems anyway; you end up with piles and piles of HTTPS/JSON/JWT overhead.
using any kind of architecture pattern can of course have these problems, to be fair... it's just more prevalent with microservices because it becomes a catch all universal tool, just add another "microservice".
before long you have competing services that have the same purpose just because people can't evolve systems in place. worse are saga patterns and phased commits, etc...
there's an XKCD for that I'm sure, the one about standards would fit.
anyway, I appreciate the points in the article that gesture towards Conway's law or inverse Conway maneuver; it's best when your org/team/project structure align w/ architecture, and vice versa. architecture isn't just about software and deployments, it's also about process, alignment, and evolution.
https://c4model.com/diagrams/deployment
that being said I consider that an implementation detail.
too much negativity in this thread!
if you have nothing nice to say just don't say anything at all.
about 10 years ago my wife and I wanted to make a card game something like a twist on cards against humanity or madlibs, that could be played in person or remotely. I built a back-end and protocol for organizing and conveying cards and such, and she got all the content put into the backend, and my buddy started on a mobile front end. my vision was to build it very abstractly, like a card game framework, so it could be any card game (and users could even make their own games). one mode was to use a tablet as the deck on the table and then everyone can hold their hand on their phones.
unfortunately, life got in the way, priorities changed, and we never finished it.
I had this idea that we could sell/license packs of card content by actual physical card game publishers... phase 10, uno, CAH, etc...
don't let the jerks here get you down, I for one appreciate this project (in spirit, haven't looked at the code) and might try to use it to finish our game one day.
thank you for sharing!
subsonic low calibur suppressed rounds don't cycle well. going for the slide without hesitation means the shooter has had weapons training imo.
this should work with limesdr as well.
for something cheaper, try antsdr or adalm-pluto: https://github.com/srsran/zynq_timestamping
lots of good notes here: https://www.quantulum.co.uk/blog/private-lte-with-analog-ada...
Makes me think of intellectualization...
> In psychology, intellectualization (intellectualisation) is a defense mechanism by which reasoning is used to block confrontation with an unconscious conflict and its associated emotional stress – where thinking is used to avoid feeling.
> Like rationalisation, intellectualization can thus provide a bridge between immature and mature mechanisms both in the process of growing up and in adult life.[14]
> Donald Winnicott, however, considered that erratic childhood care could lead to over-dependence on intellectuality as a substitute for mothering;[15] and saw over-preoccupation with knowledge as an emotional impoverishment aimed at self-mothering via the mind.[16]
It's certainly a form of dissociation, but I think in the case of the author, and others with a similar sentiment here, it's more conscious and intentional, than unconscious.
Surely a conscious choice to escape into intellectualism/information at a young age could lead to training of your thought processes/patterns such that it does become an unconscious act. Regardless of choice, I think it's an interesting parallel to draw, still...
i believe around the same time the empire state building was constructed as well.
Submitted a 10 page opposition complete with citations. Thanks for the help ChatGPT.
i did look at this when i was trying to decide on an alternative before i just bought another barley used pixelbook with only 50 battery cycles.
it's half the price so if it works for you, great! but it's no pixelbook replacement imo
https://en.m.wikipedia.org/wiki/Autophagy
https://en.m.wikipedia.org/wiki/Secondary_succession
https://en.m.wikipedia.org/wiki/Restructuring
https://en.m.wikipedia.org/wiki/Code_refactoring
https://en.m.wikipedia.org/wiki/Shiva
https://en.m.wikipedia.org/wiki/Tandava
it's all the same shit
https://en.wikipedia.org/wiki/C4_model
Level 1: System context diagram
Level 1, a system context diagram, shows the software system we are building and how it fits into the world in terms of the people who use it and the other software systems it interacts with.
Level 2: Container diagram.
Level 2, a container diagram, zooms into the software system, and shows the containers (applications, data stores, microservices, etc.) that make up that software system. Technology decisions are also a key part of this diagram.
Level 3: Component diagram
Level 3, a component diagram, zooms into an individual container to show the components inside it. These components should map to real abstractions (e.g., a grouping of code) in our codebases.
No need to go deeper considering your audience.
it's an i7 chromebook with 16GB RAM and 500GB ssd. that's still unheard of to this day...
runs linux apps natively
runs android apps natively
runs windows apps through linux/wine/steam layer
it's lightweight (2 lbs), very thin and fanless
has a high DPI touchscreen
3:2 aspect ratio
the battery lasts 10+ hours
it can be folded over into tablet mode and supports a wacom stylus
it's a chromebook so it's secure, and i don't have to fuss w/ drivers, or linux dependency hell... it just works, but lets you dive into the guts through containers if you want it.
this is a laptop from 2017, mind you... it's 2024 now, and there is still nothing else like it, 7 years later. it's kinda sad...
as usual, google pushes the boundary, and then kills the product. it was supposed to spur other manufacturers to do similar things but that hasn't happened.
there are various assortments and combinations of machines, chromebook or plain PCs that run windows/linux, but nothing actually hits all the marks: high dpi, powerful CPU, lots of memory, touchscreen, small and light, fanless, with a long-lasting battery.
there's nothing else like it.
you can find medium-DPI chromebooks with 4-8GB of RAM, and no touchscreen, and fans, with crappy batteries. you can find 16GB RAM chromebooks w/ FHD (low DPI, and no touchscreen). there are chromebooks w/ 8GB RAM, no touchscreen, high dpi, and fans... there are all sorts of combos in between, but nothing is the form factor of the pixelbook with the features it has. i don't want a plastic piece of crap that breaks.
the closest thing is a macbook air, perhaps, but apple will never make touchscreens on laptops because they want to sell people ipads and macbooks