kaio

Key takeaway:

>>The reported incidence of (epi-)myocarditis after vaccination is low and the risks of hospitalization and death associated with COVID-19 are stated to be greater than the recorded risk associated with COVID-19 vaccination [29].

I hope the research continues to make it even more safe.

Key takeaway:

>>The reported incidence of (epi-)myocarditis after vaccination is low and the risks of hospitalization and death associated with COVID-19 are stated to be greater than the recorded risk associated with COVID-19 vaccination [29].

> You may not agree with a sound money economy, and you may like the idea of a central bank that manipulate the market to encourage spending and discourage savings.

For me its actually the opposite: I feel like crypto markets are much easier to manipulate- so its done more often. I would also expext that a currency is used in daily life and not saved as form of high risk investment

So while I don't think that Banks operate for the benefit of mankind, I don't see where Cryptocurrencies would help, either. And to be fair the most real-world contact I had with Bitcoin are All of criminal nature - So there is definitely a certain negative bias

That is the key: stating the obvious actually is hard and I think Rich does a beautiful job to translate the thoughts and feelings most programmer have into words. It actually gives a way to discuss and think about things (especially design and architecture) with others. I learned that there is no such thing as "common ground" or common knowledge magically and intuitively shared by all programmers. So if this already reflects your thoughts - even better.

This article seems a bit arrogant. But I have to acknowledge that they pioneered the trend of microservices in terms of overcomplicated designs and slowness.

Honestly. Some of the most horrifying systems I have worked with were based on the idea that you should be able to swap implementations during runtime. That was the time when OSGi was the thing and (like mentioned in the article) there seem to be only a few how to use OSGi properly. I'm a burned child and certainly don't have the knowledge, either ...but the blog post doesn't give a single reason to change that.

That article is really awfull in expressing the root cause of the authors unhappiness with agile and enterprise scrum. Jira is just a tool. To stick with bad anaologies: how can a screwdriver be an antipattern?

Does the combination of Clojurescript+HTML count? [1]

[1] https://reagent-project.github.io/

Did you had a look at sqlx? [1] Granted, it won't generate the queries for you - but parsing into structs works 95% of time without additional mapping for me. Coming from other languages I also found the amount of necessary typing a bit disturbing first. But then you can actually read code instead of orm framework documentation, issue trackers and workarounds.

[1] http://jmoiron.github.io/sqlx/

Why should it be mentioned? FRP itself isn't an architecture. And as far as I know a lot of RxJava would easily fit into the "Observer pattern" (which is mentioned in the article)

I seem to miss the point why this is huge. Why can't the project compiled for Windows in first place? Are there System specific calls?

Yes, but not in the formal sense. And i don't get why agile and proper documentation should not go Hand in Hand. There are components and class Diagramms that are invaluable for me when i'm joining an existing code base. Even if they are not up-to-date everytime.

State and sequence diagrams are really cool to discuss dynamic flows and identify potential logic holes. UML-like diagrams are way better then to come up with your own representation of this everytime

That seems to link to another blog entry.

HP with webOS :). I really loved it. But it looks like you will need a really long breath to get attention and developers on your side for any new OS.

Whoa. I have been working on larger web apps at pre- react\ angular\vdom time and i'm really glad i don't have to read tons of tutorials about what might cause my Browser to repaint or even reflow the entire doc to get some Good enough performance. And react really shines for bigger projects since you only care of locale components.

Agreed. But then again i'm not sure what would be the best way here to meet everybodys needs and was hoping for a discussion: While forking is encouraged by Git(Hub) it also tends to fragment the community. So i see Jimmys points but it also puts a lot of burden on the already update-plagued react-router users.

Why do you feel this is bad? If you use my personal data and score me with some obscure system, i think it is just fair to tell me. If you score me bad, i deserve at least to know it before i run into problems Ok.. for a dating app it might not be that important but rating systems like the schufa(credit trust network) already have big influence on my daily live.

Yep. I think the more interesting stuff for developers is here: https://share.oculus.com/developer-distribution-agreement

Welp. The code would add the user himself as his own coworker in both versions.

I'm a Java programmer by day, but i have definitely learned a lot by writing some "functional" (i.e. in a "functional" language) code as well. But this is just concepts. You can also take those concepts and write clean (and not too bloated) OO code. I really don't get what all this exaggerated "functional programming" vs. "bad object-oriented enterprise code" ranting is good for

Wiki-Entry:

"The purple-facebook project simply back-ports the purple3 plugin to purple2 [..]"

So i guess you won't see the actual protocol implementation in this repo but only the necessary patches.

I'm rather confused about the capabilities... the terms BLE and (i)Beacon seem to get mixed up several times on the website. So are there any benefits compared to other iBeacon provider (e.g. Roximity , which also comes with an API and Admin panel..)?

I really would love to see full-BLE enabled devices (GATT etc).

Edit: I stumbled upon the following sentence: "Once setup, Beacons will continuously broadcast a signal (similar to a radio station) to create a mesh network connected to our platform and API."

Is a bunch of emitting beacons _really_ a mesh network?

I'm pretty sure a lot of developers would be more than happy with "only" 500K downloads ... especially with only a few supported devices like this. Makes me wonder if a lot of negative ratings is just another marketing strategy. "You have to see how crappy this app is"

Same for me. I hope this will not happen to the people actually using this application.

Makes me wonder if there are any good reasons to support both [capturing, bubbling] ways of event propagation. I think the default W3C model does a pretty good job and is more consistent with the concept of the DOM _tree_ Mixing these two modes also seems to be a good source for hours of bughunting :~

> The OP is right that mainframes aren't available to learn on.

We have a mainframe in our university (donated by IBM) which is used exclusively for teaching. As far as i know, this isn't the only one here in Germany. Allthough the material isn't as omnipresent like tutorials for beautifull HTML pages, one can sure find some. It's probably that most of the material is hard to find and not really sexy.

In case you are interested (only in German, though): http://jedi.informatik.uni-leipzig.de/de/access.html

As interesting it may ever sound, i still can't think about good use-cases for those kinds of translation tools. I have been fiddling around a bit with XMLVM (which gives really has a nice generic approach) but the point that you basically can't use any libraries leads quickly to a dead-end. Also i'm not convinced that any automatic translation of plain business-logic could compensate the sacrifice of Obj-C features.

You shoudld try http://www.phonegap.com/