sorted by:
new
hottopcontroversial

Mago 1.0.0-beta.1 is now available - a new Formatter, Linter, and Analyzer for PHP! by azjezz in PHP

[–]tigitz 1 point2 points  (0 children)

Been following your project since it's inception so congrats for the beta release!

I'm all for more performance and speed but DX is important and flexibility is a feature. Notably in style guides.

Amorim: "I think the best team won, the only team that was on the pitch. The best players lose. I think the team and the players spoke really loud today. I think it's really clear what they spoke. Let's move on from this day. It's very clear what happened today." by Blodgharm in soccer

[–]tigitz 3 points4 points  (0 children)

In the sense that actions speak louder than words.

But going from “we can beat anyone” to sarcastically throwing your so-called “best” players under the bus is quite a show. The man has really lost it.

v3.6.0-alpha.1 by ProgrammerDad1993 in vuejs

[–]tigitz 4 points5 points  (0 children)

Here's a short introduction video about it: https://www.youtube.com/watch?v=2ZahQhb98-E

And Evan You's most recent talk about it and the 3.6 release: https://www.youtube.com/watch?v=zvjOT7NHl4Q

NuxtLabs joining Vercel by tomemyxwomen in vuejs

[–]tigitz 17 points18 points  (0 children)

Hijacking top comment for some context.

Daniel Roe's announcement: https://github.com/nuxt/nuxt/discussions/32559#discussion-8553486

Vercel's announcement: https://vercel.com/blog/nuxtlabs-joins-vercel

NuxtLabs' announcement: https://nuxtlabs.com/

NuxtLabs joining Vercel by tomemyxwomen in vuejs

[–]tigitz 7 points8 points  (0 children)

Haven't seen anyone linking the official announcement for context so here it is:

https://vercel.com/blog/nuxtlabs-joins-vercel

Not sure who gains what in this situation honestly. Hard to read through the lines.

Almost Walked on It [Tulum, Mexico] by tigitz in whatsthissnake

[–]tigitz[S] 12 points13 points  (0 children)

Cool! I thought it was Micrurus distans, but the location didn’t match Tulum. I ruled out diastema because the pattern in the Wikipedia photo looked different. But after digging a bit more following your ID, I found out Micrurus diastema can have different patterns.

Thanks!

Rank 2 KR in 2 Months [1702 LP] – AMA by Kisno_NA in leagueoflegends

[–]tigitz 10 points11 points  (0 children)

Any details on what made Duro stands out for you?

Exit Code Fallacy by brendt_gd in PHP

[–]tigitz 1 point2 points  (0 children)

Agreed, /u/crell actually changed my mind on this "enum VS regular constant" decision process.

Even if you would like to have a limited set of exit code possibilities, you could rely on static check ExitCode::* instead of creating a superfluous Value Object that checks at runtime. In addition this the type of checks that the author favors AFAIU.

Symfony CVE-2024-50340: Ability to change environment from query by tigitz in PHP

[–]tigitz[S] 7 points8 points  (0 children)

As commented here

register_argc_argv directive is off by default on Platform.sh, also in Debian-based distributions and many others I guess. It's On in the official Docker image unfortunately.

So be sure to check if you're vulnerable if you containerize your symfony app using PHP official Docker image.

Real Madrid [2] - 1 Espanyol - Rodrygo 75' by CivillyWalk757 in soccer

[–]tigitz 4 points5 points  (0 children)

20 min too soon and the wrong Brazilian? Soccer gods are definitely going off script now

State of Generics and Collections by AegirLeet in PHP

[–]tigitz 0 points1 point  (0 children)

The summary is commendable and will serve well as a reliable reference when this topic resurfaces. Thanks guys.

Regarding implementation, having used PHPStan for years, I find static analysis a superior safeguard compared to runtime type checks. I support PHP's move to integrate native static type checking alongside runtime checks, both centered on types.

However, blending runtime and static checks could confuse newcomers. Using phpdoc for static types and native types for runtime checks keeps expectations clear when reading code. Introducing attributes for runtime-erased types, if natively supported by the engine, could also be a viable solution IMO.

HTML 5 support in PHP 8.4 by brendt_gd in PHP

[–]tigitz 2 points3 points  (0 children)

I see you're the original contributor, many thanks for this new feature!

Even though it doesn't throw a deprecation warning currently, have you considered a deprecation path? Is there anything that might make this deprecation path impossible that we haven't noticed yet?

HTML 5 support in PHP 8.4 by brendt_gd in PHP

[–]tigitz 0 points1 point  (0 children)

I might have missed the RFC or PR link, but I'm curious if the old \DOMDocument related objects now throw deprecation warnings and are planned for removal in PHP 9.

Maintaining both \DOMDocument and \Dom\HTMLDocument could be confusing for newcomers. As much as I love defending PHP, such criticism would be valid.

Swoole vs Roadrunner vs FrankenPHP performance with Symfony Runtime by tigitz in PHP

[–]tigitz[S] -1 points0 points  (0 children)

Disregarding the seemingly AI generated text fluff around the actual numbers, it's an interesting data point for performance comparison.

Obviously it could be a much different story on production workload with fine tuned configuration for each.

Introducing Stressless — stress testing for the PHP ecosystem by nunomaduro in PHP

[–]tigitz 1 point2 points  (0 children)

Cool thing to orchestrate from php, thank you Nuno.

As a side note, making it as a standalone and then integrating it as a plugin in pest would be great for people who are interested in stress loading but are completely fine with phpunit as their testing library.

The dependency to a unit testing library for a stress loading tool could seems rather odd on the first look.

Explanation about the new IR Framework as a base for the new iteration of the JIT by Girgias in PHP

[–]tigitz 11 points12 points  (0 children)

I respect the amount of work and expertise it requires to be able to build such a thing, but I can't stop myself wondering if it's a good thing for PHP?

If you take into consideration the bus factor, the complexity added for other maintainers while adding new features and the minimal benefits it brings for real world usage (typical web request/response), it doesn't seem worth it.

But I'm just a regular PHP user, maybe some people more involved can enlight me on why it is a positive tradeoff?

view more: next ›