27 Matching Annotations
- Apr 2022
-
github.com github.com
-
There is something nice about aligning with the platform. But it risks being a straitjacket, and I think we can provide better ergonomics when it comes to streaming.
-
- Mar 2021
-
news.ycombinator.com news.ycombinator.com
-
Clearly JS and NPM have done a lot RIGHT, judging by success and programmer satisfaction. How do we keep that right and fix the wrong?
-
-
-
Rails still encourages you to dump all validation errors at the top of a form, which is lulzy in this age of touchy UX
-
-
trailblazer.to trailblazer.to
-
signal.to_h[:semantic]
Why not just allow us to call
signal.semantic
?
-
- Feb 2021
-
trailblazer.to trailblazer.to
-
In combination with [Track()], the :magnetic_to option allows for a neat way to spawn custom tracks outside of the conventional Railway or FastTrack schema.
Instead of
magnetic_to:
, I propose wrapping the steps that are on a separate track in something like...DefTrack do :paypal do step :charge_paypal end
or
paypal_track = RailwayTrack do :paypal do step :charge_paypal end
so we can reference it from outputs, like we can with tracks created with
Path
helper.
-
-
github.com github.com
-
account.first_name = first_name if first_name.present? account.last_name = last_name if last_name.present?
I guess this is needed so we don't reset to nil (erasing value in database) when they haven't even provided a new value as input.
But surely there's a cleaner way...
-
-
-
It makes me happy to see people actually think about things and not just accept a shitty API.
Tags
- describe the ideal hypothetical solution
- doing something without knowing why/how it works
- less than ideal / not optimal
- intentional/well-considered decisions
- actually consider / think about how it _should_ (ideally) be
- "makes me happy when ..."
- can we do even better?
- don't settle for/accept something that's not as good as it can be
Annotators
URL
-
-
www.youtube.com www.youtube.com
-
considering PopOS is trying to tackle Ubuntu they really need their dual-boot setup to be a lot less tedious
-
if PopOS! really wants to be what Ubuntu was 10 years ago they need to step up and make dual booting easier.
-
- Nov 2020
-
acorwin.com acorwin.com
-
The answer should be: you write a language that compiles to Go’s IR.
-
-
github.com github.com
-
This nested if blocks seems a bit untidy and confusing to me but I've also failed to come up with a clearer way.
Tags
Annotators
URL
-
-
-
I encounter this problem in all of my Svelte projects- feels like I'm missing something. Fighting it with absolute positioning usually forces me to re-write a lot of CSS multiple times. Is there is a better way to solve this that I've overlooked?
-
-
github.com github.com
-
This is very annoying and I think there must be a better solution.
-
- Oct 2020
-
english.stackexchange.com english.stackexchange.com
-
In the software industry we use "dependency" to refer to the relationship between two objects. We say "looking for dependents" for relationships to dependent things and "looking for dependencies" for relationships to prerequisite things, so it gets that connotation, but the literal meaning is the relationship itself, not the object. Finding a better word is exactly the point of the question
-
-
dylanvann.com dylanvann.com
-
Svelte should make something like useEffect part of the framework so that this could work better and be less verbose.
-
I do like the direction Svelte is heading but I think this is one area that could be improved.
-
-
github.com github.com
-
I'm suggesting there should be a way to write lifecycle related code that also responds to changing props, like how useEffect works. I think how React handles this could be a good source of inspiration.
-
I think it just needs a few changes, possibly non-breaking additions, to be as powerful as hooks, when it comes to abstracting lifecycle related logic, and making it easy to keep effects in sync with props.
-
I'm not sure I understand the problem, everything you are describing is already possible.
-
If Svelte came up with some kind of hooks like API maybe it could solve both these issues at once.
Tags
- excellent writing
- use as inspiration
- learning from others
- issues: not taking the time to really understand the issue before closing
- issues: discuss more before closing
- too quick to dismiss
- investing time to really understand something
- copying ideas from another project
- copying/doing the same as how another project/library did it
- Dylan Vann
- feature proposal
- inspiration
- can we do even better?
- learning by studying/emulating/copying others who do it well
Annotators
URL
-
-
dylanvann.com dylanvann.com
-
I’d still be interested in Svelte making things easier so I’ve opened a feature request for Reactive statement cleanup functions.
-
-
-
It was clear no one was interested in what I was working towards.
-
Very few were interested in furthering the platform in the places they just took for granted.
-
- Sep 2020
-
stackoverflow.com stackoverflow.com
-
do I really have to do something like that in order to have my local modules working? it's quite impracticable to explain it to a team! there's nothing a little bit more straightforward?
-
-
github.com github.com
-
DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.
-
-
github.com github.com
-
But what we should ask is "can we do better than the others".
-
-
github.com github.com
-
But this is a case where it feels like we're papering over a deficiency in our language, and is the sort of thing detractors might well point to and say 'ha! see?'.
-