Search
481 results for “develwithoutacause”
-
Great post on #ClosureCompiler, it's history at #Google and how it evolved compared to #TypeScript.
https://effectivetypescript.com/2023/09/27/closure-compiler/
I can help with one of the last points:
> True to form, this tool [tsickle] is open source but pretty inscrutable to an outsider. It may be used by Angular but I couldn't tell.
I can confirm that Angular does *not* run `tsickle` or Closure in user projects with `ng build`. There was an experiment some years ago where we tried this to see if we could improve bundle sizes, but found that asking users to write Closure-optimizable code was too difficult and hard to justify outside Google. As a result, we never ran this in prod.
I believe we do technically run `tsickle` in Angular GitHub repositories, as we have a unique build system setup with #Bazel and #rules_nodejs. If you've ever contributed to Angular, you probably ran `tsickle`. We've been trying to remove this dependency, but I don't think it's happened yet.
-
CW: #EldenRing #ShadowOfTheErdtree Final Boss
I'll have to cheat #Radahn back to life just so I can have a real opportunity to learn his phase 2 moveset.
Other than that, I'm excited to try out some more new weapons and builds. Lots of cool stuff in the DLC for sure!
-
CW: #EldenRing #ShadowOfTheErdtree Final Boss
So #Radahn was definitely cool and has a pretty interesting moveset however I think is scaling is utterly messed up. I found him to be impossibly tanky until I respecced into a completely different build and then beat him in 15 minutes.
I basically had a #Rellana build going in using her twin swords. Except these swords absolutely suck against him. The light and heavy attacks are too slow to punish many of his lighter moves and don't do enough damage in the bigger windows. Uncharged R2 is usually the best option, and it's not great.
Moon-and-Fire Stance fares a bit better. The magic projectile is a decent punish and the flame spiral does significant damage. But none of his moves can really be punished by the full spiral, he always trades a blow with you. In phase 1 that trade is *usually* worth it, but phase 2 utterly wrecks you eliminating that option and heavily nerfing your damage.
-
Anyone have any good home camera recommendations? I've been using #Nest but frankly I just don't think it's a very good deal.
* The #GoogleHome and Nest apps have different features I can't make sense of.
* Apparently #NestAware lost 24/7 video history at some point.
* Event history is super precise. I can't rewind even a few seconds before an event was detected.
* It's expensive: Aware is $80/yr, Aware+ with 24/7 video is $150/yr.
* The app has really poor performance and is awkward to use (performance has gotten better lately but still not great).
* Never really figured out how to export videos correctly.I just don't like it and think I'm overpaying for this. Are there better options out there?
-
Looking into the current state-of-the-art for #NodeJS security and I'm kind of baffled by how primitive it is compared to browsers.
* No #TrustedTypes.
* No `SafeHtml`.
* No #ContentSecurityPolicy.
* No permission abstractions.
* Not even a way to ban `eval()`.Best thing I've found is `--frozen-intrinsics`, which is interesting, and I don't think there's a browser equivalent. You still have to freeze `globalThis` though to get much value out of it.
https://nodejs.org/en/docs/guides/security/#monkey-patching-cwe-349
There are also some interesting security policies, which look like they have a lot of potential. However they're all experimental right now and seem focused on code integrity.
https://nodejs.org/api/permissions.html
This this really the state-of-the-art for #Node security right now? Am I missing something?
-
Just wasted an hour debugging why:
```BUILD
load("@aspect_rules_ts//ts:defs.bzl", "ts_config")
load("@npm//@bazel/typescript:index.bzl", "ts_config")ts_config(
name = "tsconfig",
src = "tsconfig.json",
)
```Wasn't working as expected.
Apparently #Bazel #Starlark is just ok with loading the same symbol from two different locations and has no complaints! 🙃
-
It's incredible to me just how many #banking applications have completely distinct user accounts for different parts of their system. Just setting up a new account now and it was the *third* login screen I found which was the correct one. The first two gave no indication I was on the wrong login either, they just didn't work.
I can only assume this is a product of #ConwaysLaw. It would be hilarious if it weren't so depressing.
-
Are #VideoGame #remakes just an exercise in the #ShipOfTheseus thought experiment?
https://en.wikipedia.org/wiki/Ship_of_Theseus
A remake literally rebuilds the original one wooden plank at a time. Developers need to figure out the "identity" of the game and stay true to it in the remake.
* If the remake is too close the original, why bother with the remake? All the planks are still deteriorated.
* If the remake is too far from the original, it's not the same game. I loved the ship's figurehead, and when you redesigned that from scratch, it might be even more beautiful, but it's no longer the same ship to me.Developing a good remake is all about rebuilding the Ship of Theseus without losing the core identity players originally connected with.
-
As for what I hope would be next (keep in mind I did not play #RE2Remake or #RE3Remake): I don't think it's worth remaking #RE5 given it's general reception. I'd much rather see this team make a brand new Resident Evil game in this engine. They've clearly got a solid track record at this point and we never really got a "good" over-the-shoulder RE game after 4 (until the remakes).
I'd love to see an entirely new, from scratch experience built with these mechanics and engine as a starting point.
This does kind of put the team in the same position as the RE franchise was post-RE4, where they previously fucked it all up. However, RE4 was a very unique "lightning in a bottle" moment where it got so many things right on the first try. Now that we've had several games of bad ideas and the RE 2/3 remakes, I feel like we should have a better sense of what does and doesn't work which will hopefully lead to a better end product than RE5 was. Just what I'd like to see anyways.
-
All that said, #ProjectAstra was legitimately a really cool demo. And the "one more thing" bit at the end was clearly set up to asage any fears that it was a cherry-picked and sanitized environment.
The clear implication to me (having never seen this tech before, I don't have any insider knowledge here) is that putting this on an #AR headset (*cough* #GoogleGlass) with enough context about your life could turn it into a really compelling personal AI.
I'd love to have my own #Jarvis or #Cortana and that's what direction this seems to be moving. I can't wait to see how this tech evolves in the future.
-
@josep Personally I'm partial to #WebDriverIO since it actually uses the #WebDriver specification and is a little more future-proof as a result IMHO. Also comes with #Angular integration!
```
$ ng add @wdio/schematics
``` -
I've always preferred `function`-style over lambda style (`() => {}`) for named functions in #JavaScript because I think it's less confusing for newcomers and you can take advantage of #hoisting which can be a useful feature.
However, thinking about it again, hoisting can also lead to a lot of confusion as it leads to temporal dead zone which can be super confusing, even to experienced developers.
```
doSomething();
let value = 1;
function doSomething(): void {
// ERR: Cannot access 'value' before initialization
console.log(value);
}
```Based on that, I wonder if lambda style might actually be less confusing for new JS devs just because it avoids that entire class of footgun.
In practice I find this kind of issue to be relatively rare, but maybe new devs encounter it more frequently than I think.
I guess the question here is: Is JS function hoisting a useful feature or an antipattern to avoid?
-
@slightlyoff I use #JSON5 in a Chrome Extension I own solely to comment the manifest and it works great.
I do think the bigger issue is that JSON is a terrible configuration language (but great wire format!). We should be using #TOML, #YAML, or something else more targeted for that use case.
-
@slightlyoff I use #JSON5 in a Chrome Extension I own solely to comment the manifest and it works great.
I do think the bigger issue is that JSON is a terrible configuration language (but great wire format!). We should be using #TOML, #YAML, or something else more targeted for that use case.
-
@slightlyoff I use #JSON5 in a Chrome Extension I own solely to comment the manifest and it works great.
I do think the bigger issue is that JSON is a terrible configuration language (but great wire format!). We should be using #TOML, #YAML, or something else more targeted for that use case.
-
@slightlyoff I use #JSON5 in a Chrome Extension I own solely to comment the manifest and it works great.
I do think the bigger issue is that JSON is a terrible configuration language (but great wire format!). We should be using #TOML, #YAML, or something else more targeted for that use case.
-
@slightlyoff I use #JSON5 in a Chrome Extension I own solely to comment the manifest and it works great.
I do think the bigger issue is that JSON is a terrible configuration language (but great wire format!). We should be using #TOML, #YAML, or something else more targeted for that use case.
-
I want a #SuperSmashBros-clone where all the characters are mascots from children's cereal.
Imagine a battle royal between the #LuckyCharms leprechaun, #ToucanSam, the #Trix rabbit, and #TonyTheTiger.
-
#Idea: Open a new #GoogleDoc and write out a bunch of bullet points about a document/memo/essay you want to write then click "Extensions > Convert to Prose". This would call #ChatGPT (or whatever) and convert those bullet points into a full doc which structures the ideas, elaborates a bit, and provides a concrete starting point.
I know I always start docs with a bunch of bullet points and slowly expand on them. Having a robot start that process would help get complex ideas on paper and help with the "blank document" problem.
-
Just published #HydroActive v0.1.4 with #ShadowDOM support!
https://github.com/dgp1130/HydroActive/releases/tag/releases%2F0.1.4
Now you can call `host.shadow.query('...')` to easily scope a query to the shadow root of an element.
-
What even is #hydration?
I just published a new video update on #HydroActive exploring exactly what the term means, what problems you encounter when you hydrate with plain #WebComponents and how HydroActive can help with those problems.
I also give an overview of the `defer-hydration` community protocol and how we can use it provide a common hydration interface.
-
Recorded another video for #HydroActive today! This one will be focused on what exactly #hydration actually means and how HydroActive helps you solve some key problems with it.
I think the audio should come out better this time, so it's hope it works out 🤞.
-
New release of #HydroActive re-works some of the DOM access APIs and improves overall hydration support with more comprehensive examples.
https://github.com/dgp1130/HydroActive/releases/tag/releases%2F0.1.1
My next milestone is put together another video which walks through the changes and some of the design decisions which went into hydration and the weird nuances it transparently solves for you in ways you would never notice as a user. Very interesting discussion coming! 😁
-
Published: New #YouTube video on #HydroActive where I:
* (re)introduce what HydroActive is (a webcomponent library for adding hydration and reactivity to primarily server-side rendered content)
* discuss the problems it's attempting to solve
* explain the core design principles behind the project
* demo some basic components and use caseshttps://youtu.be/kTDgjF4a_oU?si=_EKTTgt6mzVyCMjg
While this is retreading some old ground from my previous video, the goal here is to kick off a series of (hopefully shorter) videos on specific concepts in HydroActive and how it evolves over time. Stay tuned for more content in the future!
-
Been struggling a lot with staying motivated with anything lately.
I've been sitting on a 90% done #YouTube video on #HydroActive but can't quite bring myself to get it over the finish line.
No games have really grabbed my attention. I tried #Prey and I can tell it's good, but just failed to grab me. I think I'm just not in the right mental state right now to enjoy it.
I've been watching #EldenRing #BingoBrawlers which is good time sink, but doesn't exactly make me feel productive. I tried a bingo seed myself, but I feel like it has a pretty high barrier to entry.
Maybe I could get back into a #Zelda #Randomizer? At this point I'm basically just waiting for #ShadowsOfTheErdtree to come out.
Anything that's worked for you to build motivation and passion?
-
@oxharris @fabrice @slightlyoff Interesting stuff, glad to see more innovation in this space. It's a unique approach for sure.
The reactivity stuff you're talking about reminds me a lot of #HydroActive, which tries to tackle a similar problem in a very different way.
https://github.com/dgp1130/HydroActive/
The HTML modules stuff is interesting. I've been doing similar explorations in this space recently which might be relevant to you.
-
Recorded a new video for #HydroActive the other day and working through editing it now.
So far I've learned a few things about myself:
1. I have no intrinsic sense of audio quality.
2. I say "definitely" as a filler word way too much where it doesn't have any meaning.
3. I say "not to mention" as a transition phrase like 80% of the time.Very enlightening experience overall.
-
The more I look into how #WebComponents implicitly "constructs" existing elements on the page, the more I'm convinced it's a terrible idea. It's so weird and unintuitive to have an element which already exists, has data, and is being used by the page to *then* be "constructed" as a completely different object.
#JavaScript semantics weren't designed for this and you run into some super weird edge cases with field initializers, property descriptors, and (now) decorators.
I'm sure other approaches to this problem were equally bad, so I'm not blaming the spec authors here. Just observing that I've gone through a lot of pain and suffering which comes from this one root cause in particular.
This is going to be a real problem for #HydroActive, but I'm not sure it's fixable at this point in browsers. I think I'll likely have to design around it in some capacity. Maybe I'll do a blog post to articulate all these edge cases and challenges.
-
@mdh I can definitely see the argument that better #RPC technologies would reduce the desire for the client and the server to be the same language. Though in my experience I don't think I've ever seen shared logic in the API layer beyond #TypeScript types.
The environments are so different between the browser and Node that you have to really go out of your way to write portable #JavaScript.
Server-side rendering is the killer feature which usually shares code between the frontend and backend. If we could do that without either:
1) forcing the client JS to run on the server or
2) duplicating the rendering logic on the serverthen users would have a lot more freedom to pick their preferred server language and ecosystem. #HydroActive does this.
Even if that was super successful, I doubt it would meaningfully reduce the developers using Node. JavaScript os just too big and developers don't want to context switch between different languages IMHO.
-
@jerod It's a bit early, but how about a #WebComponent library for adding hydration and interactivity without duplicating your build or rendering logic?
https://techhub.social/@develwithoutacause/109547375333703560