Cpvr

I’m currently listening to good credit by Playboi carti.

[HEADING=2]A 10x Faster TypeScript[/HEADING] The core value proposition of TypeScript is an excellent developer experience. As your codebase grows, so does the value of TypeScript itself, but in many cases TypeScript has not been able to scale up to the very largest codebases. Developers working in large projects can experience long load and check times, and have to choose between reasonable editor startup time or getting a complete view of their source code. We know developers love when they can rename variables with confidence, find all references to a particular function, easily navigate their codebase, and do all of those things without delay. New experiences powered by AI benefit from large windows of semantic information that need to be available with tighter latency constraints. We also want fast command-line builds to validate that your entire codebase is in good shape. To meet those goals, we’ve begun work on a native port of the TypeScript compiler and tools. The native implementation will drastically improve editor startup, reduce most build times by 10x, and substantially reduce memory usage. By porting the current codebase, we expect to be able to preview a native implementation of tsccapable of command-line typechecking by mid-2025, with a feature-complete solution for project builds and a language service by the end of the year. You can build and run the Go code from our new working repo, which is offered under the same license as the existing TypeScript codebase. Check the README for instructions on how to build and run tsc and the language server, and to see a summary of what’s implemented so far. We’ll be posting regular updates as new functionality becomes available for testing. [HEADING=1]How Much Faster?[/HEADING] Our native implementation is already capable of loading many popular TypeScript projects, including the TypeScript compiler itself. Here are times to run tsc on some popular codebases on GitHub of varying sizes: While we’re not yet feature-complete, these numbers are representative of the order of magnitude performance improvement you’ll see checking most codebases. We’re incredibly excited about the opportunities that this massive speed boost creates. Features that once seemed out of reach are now within grasp. This native port will be able to provide instant, comprehensive error listings across an entire project, support more advanced refactorings, and enable deeper insights that were previously too expensive to compute. This new foundation goes beyond today’s developer experience and will enable the next generation of AI tools to enhance development, powering new tools that will learn, adapt, and improve the coding experience. [HEADING=1]Editor Speed[/HEADING] Most developer time is spent in editors, and it’s where performance is most important. We want editors to load large projects quickly, and respond quickly in all situations. Modern editors like Visual Studio and Visual Studio Code have excellent performance as long as the underlying language services are also fast. With our native implementation, we’ll be able to provide incredibly fast editor experiences. Again using the Visual Studio Code codebase as a benchmark, the current time to load the entire project in the editor on a fast computer is about 9.6 seconds. This drops down to about 1.2 seconds with the native language service, an 8x improvement in project load time in editor scenarios. What this translates to is a faster working experience from the time you open your editor to your first keystroke in any TypeScript codebase. We expect all projects to see this level of improvement in load time. Overall memory usage also appears to be roughly half of the current implementation, though we haven’t actively investigated optimizing this yet and expect to realize further improvements. Editor responsiveness for all language service operations (including completion lists, quick info, go to definition, and find all references) will also see significant speed gains. We’ll also be moving to the Language Server Protocol (LSP), a longstanding infrastructural work item to better align our implementation with other languages. [HEADING=1]Versioning Roadmap[/HEADING] Our most recent TypeScript release was TypeScript 5.8, with TypeScript 5.9 coming soon. The JS-based codebase will continue development into the 6.x series, and TypeScript 6.0 will introduce some deprecations and breaking changes to align with the upcoming native codebase. When the native codebase has reached sufficient parity with the current TypeScript, we’ll be releasing it as TypeScript 7.0. This is still in development and we’ll be announcing stability and feature milestones as they occur. For the sake of clarity, we’ll refer to them simply as TypeScript 6 (JS) and TypeScript 7 (native), since this will be the nomenclature for the foreseeable future. You may also see us refer to “Strada” (the original TypeScript codename) and “Corsa” (the codename for this effort) in internal discussions or code comments. While some projects may be able to switch to TypeScript 7 upon release, others may depend on certain API features, legacy configurations, or other constraints that necessitate using TypeScript 6. Recognizing TypeScript’s critical role in the JS development ecosystem, we’ll still be maintaining the JS codebase in the 6.x line until TypeScript 7+ reaches sufficient maturity and adoption. Our long-term goal is to keep these versions as closely aligned as possible so that you can upgrade to TypeScript 7 as soon as it meets your requirements, or fall back to TypeScript 6 if necessary. [HEADING=1]Next Steps[/HEADING] In the coming months we’ll be sharing more about this exciting effort, including deeper looks into performance, a new compiler API, LSP, and more. We’ve written up some FAQs on the GitHub repo to address some questions we expect you might have. We also invite you to join us for an AMA at the TypeScript Community Discord at 10 AM PDT | 5 PM UTC on March 13th. A 10x performance improvement represents a massive leap in the TypeScript and JavaScript development experience, so we hope you are as enthusiastic as we are for this effort! Source; https://devblogs.microsoft.com/typescript/typescript-native-port/ video transcript: When you watch the interview with Anders Hejlsberg (the creator of TypeScript), it actually makes a lot of sense why Go was chosen. TypeScript is being ported to Go [08:58] "we realized, we can get to 10x with this!" Anders: In August, I started porting the scanner and the parser just to get a baseline so we could see how fast this could go and how hard it is to port from JavaScript to Go. It actually progressed pretty well, and within a couple of months we had something that we could run that would parse all the source code we have with no errors, and we could start to extrapolate some numbers from that. That's sort of when we started to realize, "Okay, we can get to 10x with this," because we get about three to three and a half times the speed from being native, and then we get another three to three and a half times from concurrency. Together, that gets us to 10x -- and 10x is pretty darn dramatic. [12:34] why not Rust? Anders: When you have a product that has been in use for more than a decade, with millions of programmers and, God knows how many millions of lines of code out there, you are going to be faced with the longest tail of incompatibilities you could imagine. So, from the get-go, we knew that the only way this was going to be meaningful was if we ported the existing code base. The existing code base makes certain assumptions -- specifically, it assumes that there is automatic garbage collection -- and that pretty much limited our choices. That heavily ruled out Rust. I mean, in Rust you have memory management, but it's not automatic; you can get reference counting or whatever you could, but then, in addition to that, there's the borrow checker and the rather stringent constraints it puts on you around ownership of data structures. In particular, it effectively outlaws cyclic data structures, and all of our data structures are heavily cyclic. [16:29] adding it all up: Go makes a lot of sense Anders: When we go down the list, we want a language that gives us excellent optimized native code on all major platforms. We want a language that has great expressiveness in data structures, allows cyclic data structures, but also allows inline data structures like structs -- so that, you know, in JavaScript everything you do with an object is an allocation, and we would rather avoid that, especially for small objects if we can store them inline. We need automatic garbage collection, and we also needed concurrency -- and shared memory concurrency. We can talk about the distinction there, because technically JavaScript has concurrency with web workers, but it does not have shared memory concurrency. I can explain why we need that for the compiler, but that was also a must. And when you look at all of that -- and then, of course, we want good tooling (we all live in VS Code, we want excellent support in VS Code, and whatever) -- when you add all of that up, Go actually ended up coming very high on the list. [19:14] why not C#? Dimitri: Was C# considered? Anders: It was, but I will say that I think Go definitely is -- it's, I'd say, the lowest-level language we can get to and still have automatic garbage collection. It's the most native-first language we can get to and still have automatic GC. In C#, it's sort of bytecode first, if you will; there is some ahead-of-time compilation available, but it's not on all platforms and it doesn't have a decade or more of hardening. It was not geared that way to begin with. Additionally, I think Go has a little more expressiveness when it comes to data structure layout, inline structs, and so forth. For us, one additional thing is that our JavaScript codebase is written in a highly functional style -- we use very few classes; in fact, the core compiler doesn't use classes at all -- and that is actually a characteristic of Go as well. Go is based on functions and data structures, whereas C# is heavily OOP-oriented, and we would have had to switch to an OOP paradigm to move to C#. That transition would have involved more friction than switching to Go. Ultimately, that was the path of least resistance for us. Dimitri: Great -- I mean, I have questions about that. I've struggled in the past a lot with Go in functional programming, but I'm glad to hear you say that those aren't struggles for you. That was one of my questions. Anders: When I say functional programming here, I mean sort of functional in the plain sense that we're dealing with functions and data structures as opposed to objects. I'm not talking about pattern matching, higher-kinded types, and monads. [23:44] typescript-go's memory consumption is HALF (!!) (while also being 10 times faster) Anders: You can have bytes, shorts, ints, 64-bit integers, and what have you -- both signed and unsigned. In JavaScript, everything is a floating-point number. I mean, you want to represent true or false? Yeah, that's eight bits for you. So, that is tough, and that is why we do all sorts of tricks in our existing compiler. At least, we can pack 31 bits into a floating-point number typically in JavaScript. But in Go, we can use all of the bits, and, by the way, we can also lay them out as inline structs and arrays. It shows that -- our memory consumption is roughly half of what the old compiler used. In these days, memory equals speed: the more memory you use, the slower you go, because the more times you hit the write barrier or the read barrier (and you blow your L cache, your L0 cache) and then you have to go get it from real memory. I often joke that in modern CPUs, each instruction takes zero cycles because of prediction -- except when it takes a thousand cycles because you hit the memory wall and have to go fetch. So, if you can condense your data structures, you're going to go faster. [58:36] the transition from JavaScript to Go is actually pretty gentle (compared to Rust) Anders: I will say, too, that the transition from JavaScript to Go is actually pretty gentle on the system. It is not a super complicated language with an awful lot of ceremony, which I would say Rust comes a lot closer to. I mean, Rust is more like a modern C++ than a modernized JavaScript, and Go is actually, in some ways, a modernized, native Python/JavaScript-like thing. Dimitri: When I used to write Go professionally for about two years, during an all-hands engineering meeting, there were some engineers complaining. One of them said it's mediocre and they just weren't satisfied with not being able to do fancy things in Go. The CTO -- I'll never forget -- stopped them and said, "You have to understand that Go is mediocre by design; it's not trying to be fancy." Anders: It's trying to be a simple language -- and honestly, it is. But the results are not mediocre. I mean, 10x -- there's nothing mediocre about that, right? So, you can do great things with this thing.

Most ad networks are usually CPM models these days. I don’t believe there’s any around that are paying cpc anymore. Google adsense also shifted to a cpm model.

Every forum is built by user generated content. It’s how forums strive and flourish. It has no effect on your revenue whatsoever. It’ll actually put a dent in your revenue if your forum isn’t generating enough revenue for those incentives.

I’m currently listening to I remember by 3mfrench. [MEDIA=spotify]track:4NDEv5Ydi3svzmwnj50GFW[/MEDIA]

What are some things that you do if you chose to monetize your website? Would you implement advertisements, an affiliate marketing system, merchandise system, private ad system, or something else? What are some of the things that you would never do in regards to monetizing your website? Has there ever been a website where you were turned off by their monetization methods?

I’m currently listening to blood on the leaves by roney. [MEDIA=spotify]track:6hpmfkG0S0qY3aXcnTI1ym[/MEDIA]

You’re not the only one. I only own one license. I don’t plan on buying another one, unless I change my mind and decide to launch another forum, but that’s highly unlikely.

This core update will mainly focus on surfacing more content from content creators. [HEADING=1]Google March 2025 Core Update Details[/HEADING] There are three pieces of unique details Google posted about this core update. (1) Google wrote the rollout "may take up to 2 weeks to complete." (2) Google wrote this is a "regular update designed to better surface relevant, satisfying content for searchers from all types of sites." (3) Google wrote they will continue "to surface more content from creators through a series of improvements throughout this year." Adding they did some efforts around this earlier and will do more later, "Some have already happened; additional ones will come later," Google said. Below you will find the third-party tracking tools and chatter within the SEO community. The story that tells is that some feel Google was testing this core update in the wild for days or weeks prior to the rollout of this update. But as of the past day or so, volatility was pretty calm relative for a core update. That being said, as of this morning, the tools are also pretty calm, again, relative for a core update.

Is there a particular type of crust that you like on your pizza? I prefer thick crust over thin.

I ate some chicken n. Dumplings.

This is why it’s not a good idea to use AI chat bots on your forum. Two forums that have been recently using AI bots on their forum have recently been smacked and lost of all of their organic traffic. [ATTACH type=full" alt="IMG_4227.png]1380[/ATTACH] [ATTACH type=full" alt="IMG_4226.png]1381[/ATTACH] This is all according to SEMrush, which means, their forums are no longer ranking on google for any keywords. Which is a bad thing as they will no longer be receiving any traffic from Google. This can lead to a total deindexing as well. Organic Search Traffic: 5 (-96%) – This means the site is getting almost no organic visitors, and traffic has dropped significantly. With 1 visibility on one forum, it means almost zero visibility on Google, meaning the site isn’t ranking well for any significant keywords.

Google has recently announced that they’re rolling out their core update for March, which may take two weeks to fully compete. https://status.search.google.com/incidents/zpmwuSwifjDjfrVdaZUx Incident affecting Ranking [HEADING=1]March 2025 core update[/HEADING] Incident began at 2025-03-13 09:00 (all times are US/Pacific). [TABLE width=637px] [TR] [td][/td] [td][/td] [td][/td] [/TR] [TR] [td]13 Mar 2025[/td][td]09:23 PDT[/td][td]Released the March 2025 core update. The rollout may take up to 2 weeks to complete.[/td] [/TR] [/TABLE]

I’d like to see a new addition to the Administrata Pro subscription where interested users can request a Reddit post in our designated subreddit to help increase their forum’s visibility and exposure. This feature could also be expanded to other social media platform

My favorite toppings are pepperoni and ham or an all meat lovers pizza. I don’t like supreme pizza nor Pineapple. I generally eat pizza every other week. Pizza hut and Dominos are my favorite along with Homemade pizza.

I usually find these projects on Reddit and another forum that I’m a member of. There’s a lot of indie developers in those spaces working on different forum software concepts. Mikeal from the 32bit community actually introduced me to Cera and FishBB, however, I found Neobb while browsing Reddit. https://discourse.32bit.cafe/t/neobb-a-new-forum-software-is-being-developed/2392/2 I think most of them can probably can get taken over by another developer if the updates slow down though. It’s interesting that there’s more options available though.

Welcome to the community!

Leaked Slack chat shows Matt Mullenweg considering delaying WordPress releases until late 2027, citing reduced corporate contributions A leaked WordPress Slack chat shows that Matt Mullenweg is considering limiting future WordPress releases to just one per year from now through 2027 and insists that the only way to get Automattic to contribute more is to pressure WP Engine to drop their lawsuit. One WordPress developer who read that message characterized it as blackmail. [HEADING=1]WordPress Core Development[/HEADING] Mullenweg’s Automattic already reduced their contributions to core, prompting a WordPress developer attending WordCamp Asia 2025 to plead with Matt Mullenweg to increase Automattic’s contributions to WordPress because his and so many other businesses depend on WordPress. Mullenweg smiled and said no without actually saying the word no. Automattic’s January 2025 statement about reducing contributions: [HEADING=1]Leaked Slack Post[/HEADING] The post on Slack blamed WP Engine for the slowdown and encourages others to put pressure on WP Engine to drop the suit. The following is a leaked quote of Mullenweg’s post on the WordPress Slack channel, as postedin the Dynamic WordPress Facebook Group (must join the Facebook group to read the post) by a reliable source: [HEADING=1]Response to Mullenweg’s leaked post:[/HEADING] One Facebook user accused Mullenweg of trying to “blackmail” the WordPress community to pressure WP Engine (WPE). They wrote that the community is largely sympathetic to WPE than to Mullenweg. But in general Mullenweg’s statement was met with a shrug because they feel that this will give core contributors the chance to catch up on maintaining the core which to them is a greater priority than adding more features to Gutenberg which many of the developers in this group apparently don’t use. One lone commenter in the Facebook discussion asked if anyone in the discussion had made a positive contribution to WordPress. At the time of writing, nobody had cared to respond. Source: https://www.searchenginejournal.com/mullenweg-considers-delaying-wordpress-releases-through-2027/541821/

Fishbb is a simple, yet minimalist bulletin board board software that’s designed for sustainable online communities. It uses go + & sqlite and no javascript along with 12 dependencies, 2,000 lines of, 2000 lines of code. FishBB is designed to require a minimal amount of infrastructure and maintenance burden for self-hosting. All FishBB data is stored in a single sqlite file. HTML templates are embedded in the Go bindary. FishBB is VERY early in development -- expect bugs and be very wary of sensitive data. Make sure to change the admin password away from default credentials. [HEADING=2]#[/HEADING] FishBB also runs as a 'cluster' where multiple forums can be created. These forums can either exist in the 'cluster' (as a sort of broader forum manager) or exported on their own. The app that hosts the fishbb cluster is https://git.sr.ht/~aw/fishbb-cluster https://git.sr.ht/~aw/fishbb

Creating a responsive website is essential in modern web development. CSS breakpoints allow us to adjust layouts based on screen sizes, ensuring a smooth experience acrossmobile, tablets, laptops, and desktops. [HEADING=1]🔹 What Are CSS Breakpoints?[/HEADING] CSS breakpoints are specific screen widthswhere your website layout adapts to different devices. They help create mobile-friendly and responsivedesigns. [HEADING=1]📌 Common CSS Breakpoints[/HEADING] Below are commonly used breakpoints for different devices: 📱 Mobile: Up to 480px 📟 Extra Small Devices:481px - 767px 📲 Small Tablets: 768px - 991px 💻 Large Tablets/Laptops: 992px - 1199px 🖥️ Desktops: 1200px - 1919px 🖥️ Extra Large Screens:1920px and above [HEADING=1]✨ How to Use CSS Media Queries for Breakpoints?[/HEADING] Use the @media rule to define CSS styles for specific screen sizes. Example: /* Mobile */ @media (max-width: 480px) { body { background-color: lightblue; } } /* Tablets */ @media (min-width: 768px) and (max-width: 991px) { body { background-color: lightgreen; } } /* Desktops */ @media (min-width: 1200px) { body { background-color: lightgray; } } [HEADING=1]🎯 Best Practices for Responsive Design[/HEADING] Use rem/em instead of px for flexible sizing. Start with a mobile-first approach and scale up. Test on multiple devicesusing browser DevTools. Use CSS Grid & Flexboxfor better layout control. [HEADING=1]🔥 Conclusion[/HEADING] CSS breakpoints are crucial for making websites responsive. By using media queries, you can ensure your website looks great on mobile, tablets, and desktops. Always followbest practices and test your designs on different screen sizes. Source: https://pixeltoinches.com/blog/css-breakpoints-for-web-developers

Running a forum comes with its fair share of drama. Whether it’s toxic users stirring up trouble, leaks causing chaos, or internal disputes spilling into public view, bad PR can hit hard. I’ve dealt with all of the above, and the key to bouncing back is owning the situation and controlling the narrative. First, transparency is everything. If something goes down, address it head-on. Don’t try to sweep things under the rug because the community will talk regardless. A well-worded announcement explaining what happened (without fueling the drama) helps maintain credibility. Second, clean house fast. If toxic users are the problem, ban them. If it’s an internal issue, lock things down and restructure. You can’t rebuild trust if the same people causing the damage are still around. Third, engage with the community. Open up discussions, answer concerns, and make it clear that you’re working on solutions. A forum is nothing without its users, and if they feel ignored or betrayed, they’ll leave. Finally, implement changes and show results. Whether it’s better moderation, stricter privacy policies, or improved communication, actions speak louder than words. If people see that you’re actively improving things, they’ll stick around. It takes time to rebuild a forum’s reputation, but if you handle the situation with honesty and strong leadership, your community will respect you for it. Have you ever had to deal with a PR nightmare on your forum? How’d you handle it?

It is a foregone conclusion that AI models can lack accuracy. Hallucinations and doubling down on wrong information have been an ongoing struggle for developers. Usage varies so much in individual use cases that it's hard to nail down quantifiable percentages related to AI accuracy. A research team claims it now has those numbers. The Tow Center for Digital Journalism recently studied eight AI search engines, including ChatGPT Search, Perplexity, Perplexity Pro, Gemini, DeepSeek Search, Grok-2 Search, Grok-3 Search, and Copilot. They tested each for accuracy and recorded how frequently the tools refused to answer. The researchers randomly chose 200 news articles from 20 news publishers (10 each). They ensured each story returned within the top three results in a Google search when using a quoted excerpt from the article. Then, they performed the same query within each AI search tool and graded accuracy based on whether the search correctly cited A) the article, B) the news organization, and C) the URL. The researchers then labeled each search based on degrees of accuracy from "completely correct" to "completely incorrect." As you can see from the diagram below, other than both versions of Perplexity, the AIs did not perform well. Collectively, AI search engines are inaccurate 60 percent of the time. Furthermore, these wrong results were reinforced by the AI's "confidence" in them. Click to enlarge. The study is fascinating because it quantifiably confirms what we have known for a few years – that LLMs are "the slickest con artists of all time." They report with complete authority that what they say is true even when it is not, sometimes to the point of argument or making up other false assertions when confronted. In a 2023 anecdotal article, Ted Gioia (The Honest Broker) pointed out dozens of ChatGPT responses, showing that the bot confidently "lies" when responding to numerous queries. While some examples were adversarial queries, many were just general questions. "If I believed half of what I heard about ChatGPT, I could let it take over The Honest Broker while I sit on the beach drinking margaritas and searching for my lost shaker of salt," Gioia flippantly noted. Even when admitting it was wrong, ChatGPT would follow up that admission with more fabricated information. The LLM is seemingly programmed to answer every user input at all costs. The researcher's data confirms this hypothesis, noting that ChatGPT Search was the only AI tool that answered all 200 article queries. However, it only achieved a 28-percent completely accurate rating and was completely inaccurate 57 percent of the time. ChatGPT isn't even the worst of the bunch. Both versions of X's Grok AI performed poorly, with Grok-3 Search being 94 percent inaccurate. Microsoft's Copilot was not that much better when you consider that it declined to answer 104 queries out of 200. Of the remaining 96, only 16 were "completely correct," 14 were "partially correct," and 66 were "completely incorrect," making it roughly 70 percent inaccurate. Arguably, the craziest thing about all this is that the companies making these tools are not transparent about this lack of accuracy while chargingthe public $20 to $200 per month to access their latest AI models. Moreover, Perplexity Pro ($20/month) and Grok-3 Search ($40/month) answered slightly more queries correctly than their free versions (Perplexity and Grok-2 Search) but had significantly higher error rates (above). Talk about a con. However, not everyone agrees. TechRadar's Lance Ulanoff said he might never use Google again after trying ChatGPT Search. He describes the tool as fast, aware, and accurate, with a clean, ad-free interface. Do you trust AI search engines to return accurate results? Source: https://www.techspot.com/news/107101-new-study-finds-ai-search-tools-60-percent.html

I’m currently listening to think of you by Taj jackson.

Spain's government approved a bill on Tuesday imposing massive fines on companies that use content generated by artificial intelligence (AI) without properly labelling it as such, in a bid to curb the use of so-called "deepfakes". The bill adopts guidelines from the European Union's landmark AI Actimposing strict transparency obligations on AI systems deemed to be high-risk, Digital Transformation Minister Oscar Lopez told reporters. "AI is a very powerful tool that can be used to improve our lives ... or to spread misinformation and attack democracy," he said. Spain is among the first EU countries to implement the bloc's rules, considered more comprehensive than the United States' system that largely relies on voluntary compliance and a patchwork of state regulations. Lopez added that everyone was susceptible to "deepfake" attacks - a term for videos, photographs or audios that have been edited or generated through AI algorithms but are presented as real. The Spanish bill, which needs to be approved by the lower house, classifies non-compliance with proper labelling of AI-generated content as a "serious offence" that can lead to fines of up to 35 million euros ($38.2 million) or 7% of their global annual turnover. Ensuring AI systems do not harm society has been a priority for regulators since OpenAI unveiled ChatGPT in late 2022, which wowed users by engaging them in human-like conversation and performing other tasks. The bill also bans other practices, such as the use of subliminal techniques - sounds and images that are imperceptible - to manipulate vulnerable groups. Lopez cited chatbots inciting people with addictions to gamble or toys encouraging children to perform dangerous challenges as examples. It would also prevent organisations from classifying people through their biometric data using AI, rating them based on their behaviour or personal traits to grant them access to benefits or assess their risk of committing a crime. However, authorities would still be allowed to use real-time biometric surveillance in public spaces for national security reasons. Enforcement of the new rules will be the remit of the newly-created AI supervisory agency AESIA, except in specific cases involving data privacy, crime, elections, credit ratings, insurance or capital market systems, which will be overseen by their corresponding watchdogs. Source: https://www.reuters.com/technology/artificial-intelligence/spain-impose-massive-fines-not-labelling-ai-generated-content-2025-03-11/

Welcome aboard ron!