Target audience might be slightly different ultimately, but we'll see - I would envision this to be more useful in an enterprise environment where you pretty much always have to customize the integrations that were provided out of the box.
381 karma · joined July 2, 2018
Target audience might be slightly different ultimately, but we'll see - I would envision this to be more useful in an enterprise environment where you pretty much always have to customize the integrations that were provided out of the box.
Feel free to check out Titanoboa on Github: https://github.com/mikub/titanoboa
Also: This is an early beta so please do let me know if something breaks or you spot a bug. Atm I have load-balancers set up only on West coast and in Europe, so apologies to folks from down under & similar locations, let me know if it's too laggy :)
Feel free to check out Titanoboa on Github: https://github.com/mikub/titanoboa
Also: This is an early beta so please do let me know if something breaks or you spot a bug. Atm I have load-balancers set up only on West coast and in Europe, so apologies to folks from down under & similar locations, let me know if it's too laggy :)
AFAIK it is not, 5G also deploys >24GHz (up to 300GHz).
Happy to be proven wrong, but so far - from my POV - this has been the biggest hole in the theory that we do not need to test 5G because we already know it is safe...
For instance couple of years ago after a surgery I had plenty of time and I watched some conspiracy documentaries (like 9/11 or chemtrails), and I was almost disappointed how quickly they crumbled (within minutes) as they were completely lacking any data or proofs - and I really was curious and open-minded and was looking forward to learn something :)
This issue however becomes much more complicated when discussing environmental and health issues - there usually the technology at hand actually should and needs to prove its safety.
However deranged some of the 5G theories are, it should not hide the fact that - afaik - there is no proper safety study for continues exposure to >24GHz. Even thought theoretically we might think it is safe, it is still paramount to fully safety test it.
So lets stop with all the straw man stuff and do some real studies (or find them if they are already out there).
Just out of curiosity: were these junior devs? Were they maybe more proficient in other language/IDE? Couldn't better mentoring/on-job training help - rather than just to "weed them out"?
I might be naive but (and I have also been on leading positions) I still believe that if it seems that somebody "cannot code" it (most of the time) just means that somebody a bit more senior just have to invest a bit of time to coach them...
Could you provide a source?
Here is how I built it into mine: https://www.titanoboa.io/cluster.html
Obviously this will not always be the right solution, but in some cases might be better fit than k8s...
Shameless plug: I built something similar as a part of my workflow platform for JVM (for Java and Clojure):
https://github.com/mikub/titanoboa
The main focus of my tool is enterprise integration and data processing, but I still love to play and experiment with the ideas of developing code directly in browser and how to visualize its execution flow. So I built a live coding / visualization also as a part of my tool. This becomes non-trivial if you apply it to languages other then js (so browser integration becomes a bit harder).
I also think the main challenge here is the server-side part of things, especially when you make such solution distributed - i.e. how you achieve high availability and assure everything gets executed (at least) once even in case of failover, how you cater for multitenancy while achieving sufficient security/isolation between users etc. edit:spelling/formatting
And yes, lung and heart toxicity are a thing so make sure doctors watch out for those.
Which regimen do you have?
Also hi to all fellow survivors!
- number of contributors :D
- titanoboa can process even a potentially cyclic graph
- in titanoboa you can write step functions directly in high level programming languages such as clojure and java (so not just bash or python) and deploy them directly during runtime
- the clustering setup in titanoboa is master-less
- titanoboa does not have such direct integration with Spark as it employs some map-reduce patterns internally
But all-in-all I have to say that DolphinScheduler seems quite nice! Also would have to compcomplement it on the nice documentation (again, just briefly skimming through it).
(edit: formatting)
The problem I usually run into is the complexity - examples of event flows almost always look super cool, but in real life scenarios, the complexity is usually huge and complex flows are very hard to visualize in an organized manner.
Whether you are talking about Event flows, BPMN or TOGAF - if your workflows reflect all the real-life complexity (e.g. booking cancellation, editing, extra charges etc. etc.) it will get almost impossible to visualize them concisely.
Shameless plug:
I wrote few blog posts on the subject and also created a workflow tool to address this problem:
- Visualizing large workflows using D3, React and Clojurescript
https://www.titanoboa.io/visualizing-workflows.html
- Revisiting workflows: BPMN is dead. Long live the Functional Programming!
Yet it is still surprising to see that on HN in general anyone questioning safety of pharmaceutical products get downvoted into oblivion.
Aside from that I was a big LightTable fan and really enjoyed its inline instarepl and other features, so it is definitely great to see that LT is not completely forgotten! Kudos!
So this is not some grieving random person from crowd - Chas is a person whose libraries and contributions I value tremendously and he certainly made LOTS of contributions to clojure OSS landscape for free and out of his good will as well. So ultimately this feels like your parents are arguing (which is never a good thing) - you like them both and you just want the arguing to stop and you just want everybody to live together in harmony. But here you go, Chas has moved away from clojure now. And I have to say I am very sorry to see him go.