So I built Gigi, a control plane for autonomous AI development.
264 karma · joined October 20, 2013
So I built Gigi, a control plane for autonomous AI development.
This enables me to share my creative thinking.
In this series of articles, I am migrating Starplot (a Python library for creating star maps) to JavaScript while exploring all the related concepts and knowledge around history, math, and astronomy.
I’ve added a bit of narrative-imagine a Tuareg sitting beneath a crystal-clear sky in the desert at night.
Let me know what you think and if you have any questions.
Anyway, I find this tools fitting a very nice niece.
I’m currently working in a similar extension of markdown.
In case, the author pass by, would love to connect.
What is your thought about? Limitations and Opportunities?
Additional Links:
This enters in the category of taste, I’m surprise that someone has investigate the assumption that could be correlated is something meaningful.
Although when comes to programming there is still different styles, compositions over inherence, condition verbalization, etc…
I wonder if that makes the difference. I believe makes better code, but some times I struggle explaining the value.
I'm currently using @arrows/composition https://caderek.github.io/arrows/packages/composition/#pipe because of the light way library approach, which you seem to share.
I also try fp-ts https://github.com/gcanti/fp-ts but is a bit an academic style, so difficult to introduce in everyday work. Implementation of pipe: https://gcanti.github.io/fp-ts/modules/function.ts.html#pipe
I still need to wrap my head on your use of generics, but yours looks more flexible than the static type approach that other libraries (include RxJS) implements, does your pipe support types for any length of arguments? Does require a specific version of TypeScript?
Nice work.
I think DRY is a good thing in some cases, but you should careful consider when something is worth to DRY and when rather WET gives you the best tradeoff for isolation.
My metrics to decide is to stick in favour of the Single Responsibility Principle. If DRY means compromising it, most likely is not worth it.
The only pragmatic argument that I could understand is the hard-wiring “issue”; which IMO is not part of FP and neither OOP but just a consequence that explicit intents are simpler than implicit intents.
I understand that this is to introduce to a novelty approach that Multix offers with cats.
But to be fair, not as sofisticate as Multix, Dependency Injection tries to tackle the hard-wiring constraints of imperative.
What I take from FP is Composition rather than Chaining, which much more flexible than the OOP counterpart, inheritance.
I was expecting to learn something new but I just jump in a spooky vocabulary that rather teach me something just waste my time.
The point stand, Multix might be a fabulous approach in coding, but this article failed to give any practical introduction to it, while claiming his superiority in something that totally didn’t resonate with me.
If your mission is getting Multix adopters I will invite you to shift your focus from language/tone/academical complexity; to something more simple, what does it solve?
This is a BOOX Note Air, with Termux + Mosh + TMUX and my editor of choice Emacs DOOM.
I'm pretty happy of this setup. I went in holiday and I manage to use my editor to do some coding.
The only side effect is that it requires internet for extra processing power, although you could still run all locally depending on your requirements.
I even try to build a prototype my self for p2p poker. I don't have anymore the code to share.
Anyway I will also recommend this video about it: https://www.youtube.com/watch?v=mthPiiCS24A
For instance one logo is the one of SpaceX, which sadly is just a user group, nothing official. Another mention is Google which I didn’t find any relevant code that gives a hint that Casbin is used by Google in production.
Someone mentions shortcuts in codes; well didn’t got the time to find back all the notes.
But we find several bugs mainly in the implementations that lead us to look somewhere else.
We end-up with CASL.
That doesn’t mean that I don’t like to use Casbin, but already cost me to much time of debugging.
But let me leave with a disclaimer for a later me:
Code mutates like nature does, what it might be true today might be false tomorrow and viceversa, and if you got the time to improve it, just use it.
Don’t get bend by this merely opinion and just investigate and form your own, and always give a second chance, because times changes everything, and sometimes nothing changes.
I’m looking for a Designer for a pet building a SaaS solutions to integrate design more into development, get in contact with me if you want to know more.
I’m also looking to someone to invest part time hours to build services that can create passive income together, a sort of business pattern of MVPs.
Is basically the same implementation, I must say that keep the instance open const me a bunch of money in the end.
I think would help everybody keeping like that. But that rise a question, why do we need an Italian HN? (this is not scepticism but just natural question) Which target is that platform aming to, different than HN already does?
Great initiative anyway!
And since a couple of days I'm getting more posts about org-mode. I think are nice foundations to continue on.
Isn't what string base templates always delivered? Precompiled template function where you need just to pass the context and just return a string? That you could compile trough a transpiler?
Feels that React went to far for solve real world problems.
Douglas Crockford, told us in 2008 that DOM manipulations were faster. And React bet on it by move all in, with in-memory tree creation and delivered diff-Patching technology.
Not per se a bad thing.
I think Node are great, but bindings on shadow are just useless expensive, and caching template-functions is a nightmare if you've to keep in mind all the 'useless' events.
This why pieces like Preact make sense to exists; and why alternatives, like diff on context (Angular) make still sense.
Although here we're talking about pre-compile patching. Which IMO you just get for free in strings templates that don't relay on a Dom in solving partials (beforeNode vs afterNode).
Unless you need to change attributes in a table of thousand elements, most of Reacts, once again, shows only overengineering and premature optimizations that don't serve the purpose.
But yeah, all React is an Hype. Still like to read it :-)
Disclaimer: I'm just saw the idea and I din't run any investigation on existing solutions.
Suggestions / Questions: - A plus would be having a "promise version" that could resolve .if() || .else || .elseif || .all || .then || .final || .catch would be awesome to be combine with generators or just async/await.
- I would love to have it, build-in of ECMAScript, so could you think of something that could fit in a draft and could be pluggable in babel? as a POC? (Would be worth it?)
- The website, by layout, says "I wanna sell you something, that has little to do with coding!" I know is about taste, but thats my feeling on it, is just a minor irrelevant thing.
Anyway I like the API that you're delivering. Nice neat syntax, I would see if during my coding I get a chance to give it a try, I would tell you the results of it.
Even if people try to sell it has flexible silver bullet, made up for everything; like any other tools around, they need to apply some sort of CAP theorem. Because underwoods we're just talking in how moving bits.
For instance I use containers like AWS lambda's functions. And I use tar streams to pass the contents inside them (So no virtualised mounted filesystem needed).
With that I mean you can find different way to use them, in short: Law of the instrument.
If you're wise (and according with you article you got ton of experience), you can find good purpose for it.
Docker is just 'meant' to make your life 'easier', like any other tool, not always they satisfy the expectations.
In other hands you gain experience with it, I'm sure you would use them back for a better purpose, where they can perform better for you, there is nothing to worry about this is just experience.
Thanks for sharing.