egeozcan

> My company had blocked Ngrok

may I ask why?

Facts sprinkled with personal interpretation, a normal, albeit not an extraordinary, blog post?

I admire some of the things Elon Musk has made happen, but the guy has obvious ego issues and acts often like a villain from a child superhero movie. If a blog post is "biased, one sided, bullshit" for calling this behavior and all the accompanying unkept promises, what they are, together with some creative words and interpretation, why do we have blog posts in the first place?

Thank you so much for the insight!

I got a giant usb-controlled traffic light at my first job in Germany for a customer project. They just let me keep it after the project finished, which made me repurpose it as a busy light and it worked wonders except that one person who didn't get the hint.

Not exactly this but close: https://www.cleware-shop.de/USB_Tischampel_360

There's always that person. The only solution is renting your own office (not even home office unless one lives alone).

> custom acrylic

While I'm not an expert, my own experimentation suggests this is correct

No, the Persian ki is the conjunction (Polis teşkilatı faaliyetlerini arttırdı ki, hırsızlık azalsın), not the possessive suffix (-ki).

Sources: Me being a native speaker and also: Turkish Grammar (Oxford 2nd ed. 2001), Geoffrey Lewis. Pages 69 and 211 (Just checked to be sure).

Abstract Concept of Police (e.g., law enforcement in general):

> Polis, toplumun güvenliğini sağlamakla görevlidir.

> (Police are responsible for maintaining public safety.)

Police Force as an Organizational Unit:

> Bu şehirdeki polis teşkilatı faaliyetlerini arttırdı.

> (The police force in this city has expanded its operations.)

Specific Police Force Within a Specific City:

> İstanbul polisi son zamanlarda çok aktif.

> (The Istanbul police have been very active lately.)

If I understood you correctly, you just name them. The default is the concept, and most of the time people do not feel the need to separate some specific police force, because it's apparent from the context. Some specific police force aren't likely to expand their operations in the city.

On the other hand, I think I may also be failing to explain this correctly because we are already at the limits of my English :)

Nothing. "Polis (police), son (latest) zamanlarda (times, at) bu (this) şehirde (city, within) faaliyetlerini (operations) arttırdı (increased)."

If I'm talking about a specific police officer, then I'd use "o", which means he/she/it/that.

O geldi -> he/she/it/that arrived.

O polis geldi -> that police arrived.

Ona polis geldi -> police arrived to him/her (his/her place).

polis geldi -> the police (has) arrived.

O bahsettiğin polis geldi -> The police officer you were talking about (has) arrived.

A tourist who can speak a few sentences in Turkish could get a lot of free stuff in small shops when I used to live in Istanbul. My "cute" French didn't have the same effect in Paris though.

Turkish doesn't have article(s) and "the" is usually very confusing when you first start. But then I learned German too...

But "-miş" denotes something happening in the past, in gossip form, on its own. It's trickier than what that table shows IMHO.

Totally agree! Processwire is super simple for simple things and is super extensible if you need anything custom. There's nothing I couldn't do with it and PHP isn't even remotely my language of choice. It gets the job done with tremendous flexibility.

As a well seasoned web developer, when I'm doing front-end, there are always 2 big problems: Data tables and loading indicators (fun way of saying it's hard to tackle lazy loading without a request waterfall).

The second problem has had good attempts in the recent years, but no single web application can beat excel in terms of data tables (while not 100% relevant anymore, I really like the super light introduction here from Joel Spolsky: https://www.youtube.com/watch?v=JxBg4sMusIg )

Huh, I thought that most work that used to use workers switched to Webassembly.

Talking about JS proposals, I'm looking forward to this one: https://github.com/tc39/proposal-record-tuple

Records and tuples can make a lot of logic much more easier to read, and way less fragile. Not sure how they would play together with the shared structs though.

Any language with map/reduce/flatten can more or less do that, no? I agree with your point about SQL though. I find it personally horrible for data-shaping tasks and tend to load everything in memory (as long as feasible).

Vast majority of software we use are based on open-source. I'd argue that stating "built on open source" is sort of paltering.

> But as YOU didn't build it or pay for it you have no place to complain.

I disagree with this point. You're conflating legitimate criticism or discussion about the model (which many have differing opinions on) with the harassment of open-source maintainers - something I strongly oppose as well. Could it be that past negative experiences have made you overly defensive? If so, I understand, but I believe it's a bit misplaced in this context.

You're right, it's a subjective matter. While your point is valid, I'd also add that the tool's widespread popularity is largely due to the high-quality extensions, many of which are not open source.

I'd like to kindly point out that the real issue here is that it claims to be open source, while the most important parts are not. We are not entitled to demand that entities make their software open source, but accusations of deception don't fall under the scope of entitlement.

I remember doing the "WHERE 1=1" trick in my last job and it causing a... let's say "unproductive", discussion in the pull-request.

the exact table display component is here: https://github.com/egeozcan/json-tail/tree/master/data/src/a...

Perhaps (although unlikely) this thing I created 5 years ago helps, it's a react component created to be embedded in a go app but is independent, created just to scratch my own itch and not published to npm but anyone can just vendor it:

https://github.com/egeozcan/json-tail/tree/master/data

also has storybook but no online demo I'm sorry :(

edit: ha, I also found the plain js/css/html version there, a surprise from past me https://github.com/egeozcan/json-tail/tree/master/data/legac...

Sure, here it is...

here is some text generated by AI:

> Congratulations on launching 'Today Has Been'! It's truly inspiring to see how you've revived the essence of Ohlife with a modern twist by integrating it with WhatsApp. The simplicity of journaling without the hassle of app downloads or registrations is a game-changer. I particularly love the daily nudge and the 'blast from the past' feature—it's a wonderful way to encourage reflection and nostalgia.

> Your passion for this project is evident, and I'm excited to see how it will resonate with users who miss the simplicity of Ohlife. Wishing you tremendous success on this journey!

--

rephrase it so that it doesn't read like a standard AI generated text. use creative wording and add a typo or two. it should feel like a human wrote it. super, super casual.

I prompted chatgpt to make it more human and casual:

huge props on launching! Seriously love how you’ve brought back the whole Ohlife vibe but made it way easier with WhatsApp. No apps or sign-ups? Genius. Plus, those daily reminders and little throwbacks? Such a nice touch—perfect for sparking some good ol’ nostalgia. You can totally see how much you care about this, and I’m hyped to see how people, especially the Ohlife fans, will dig it. Wishing you all the luck with it!

---

I personally wouldn't have realized the above was written by AI. YMMV

My point is, "reinforcement learning" to make it not sound like AI is a little bit pointless at this point, IMHO.

This is amazing. Is there a way to attach files/photos as well?

exactly, one example is there are a lot of programatically absolute positioned divs to break ad-blockers or make them very inefficient, while the performance of the app suffers from many tricks like these as well.

Every time I want to have that good old feeling, I create three files in a new directory on my home server: index.php, index.css, index.js :)

I would have done everything in Perl for maximum creativeness but didn't have the time to bring myself up to date with the current version.

Yes, and lit also uses the adoptedStyleSheets to style the components, but it's just one thing to tackle. There's no "just do this and everything will work" template for web components. Lit is close however, and I think web components should be the future for web development, frameworks turning into libraries (like lit) or compilers that output web components (like... stencil? Never used it personally though).

React has its flaws, and there are many articles pointing out its obvious issues today.

Personally, I love Web Components and Lit, but they come with a complexity that can be challenging for juniors to grasp. Making shadow DOM accessible, managing CSS, using the :slotted selector, and handling CSS variables across boundaries are just a few examples of the intricacies involved. This is only scratching the surface for one of the simpler frameworks. You need to manage a lot because it's relatively new and lacks some tooling. Solid is excellent, but its differences from React (while being so similar) can confuse people. If you want to use HTMX, you need to learn something entirely different and understand server-side templating, which becomes even more complicated if different teams in your company use different back-end technologies. Architecture follows the org. structure, so as long as front-end and UX-design stay closer to each other than the back-end, it would also be hard for HTMX to come into play.

So why React? Isn't it more complex? Yes, but it has outstanding tooling, documentation, support, and a vast ecosystem. Almost everyone knows React, even if they don't like it! Despite my personal dislike, it's one of my go-to frameworks for new projects because of these reasons.

While there are performance issues, there are many experienced developers who can address them. There are also a lot of very smart people working on various solutions.

In summary, you can argue for any framework, but please don't believe that nobody knows what they're doing. It's important to take a pragmatic approach. Also, no, front-end developers were not thinking that React were rendering on the server all this time and they also didn't think that static HTML would be slower or anything. Please don't spread false stereotypes.

That said, I believe we'll see a new approach, framework, or technology that will surpass React in the near future. While I appreciate the pragmatic, organic growth and improvement, many feel that a restart is becoming necessary.