amazedsaint

The σ8 tension remains unresolved in 2025, with CMB vs. lensing data differing by ~2-3σ. Tachyon fields show promise for DE/DM unification via negative pressure, but they struggle to lower σ8 enough without tweaking geometry. Here is a Consistent Tachyon + Λ + Background‑Safe μ(a) Pipeline - It resolves the σ₈ tension while keeping geometry intact, which ΛCDM+ν or early DE do not do as cleanly.

Proposing a new architecture for O(1) memory neural network training. ZeroActivation enables training of arbitrarily deep neural networks with constant memory usage, regardless of depth. Perfect for Apple Silicon (M1/M2) users and anyone looking to train impossibly deep models. The kicker is a new model I developed for Reverse SSA, more on that soon - Thanks

You can state what you want in natural language, like "translate file somefile.txt in documents folder from english to french" or "create a pet-store website in my xyz folder" and the plugin will accomplish tasks for you from with in ChatGPT

Here are the available commands:

/project [summary] [task] [languages] [frameworks] - Output the list of files & folder structure for the project based on the project summary, task, languages, and frameworks.

/code [filename] - Output the code for the specified filename.

/tests [filename] - Output the tests for the specified filename.

/explain [filename] [function] - Explain the given function in the specified filename.

/run - Simulate the console of the program when it is running.

/revise [filename] [modification] - Rewrite the content of the specified filename, taking the modification into consideration.

/comment [filename] [function] - Add a comment to the specified function in the specified file.

/format [filename] - Format the code within the specified file properly.

Example usage:

/project "Weather App" "Display current weather" "JavaScript" "React, OpenWeatherMap API" /code "app.js" /tests "app.test.js" /explain "app.js" "fetchWeatherData" /run /revise "app.js" "Add error handling for API call" /comment "app.js" "fetchWeatherData" /format "app.js"

Good explanation

And when I look back, I feel I should've made it OSS. The source was in a crashed hdd that I abandoned, and it was developed in VB and VC.

Cool, here is another one I wrote few years back - http://www.amazedsaint.com/2008/01/neural-networks-part-i-si...

Awesome, Zed.

Identity crisis for Windows

The real problem is, recently there are lot of instances in India where government is trying to enforce restrictions around social media more or less to protect its own interests. There are no clear guidelines regarding how you'll classify something as free speech or hatred speech. Most politicians are too ignorant about internet, social media and the emerging crowd power, and they are very anxious about the same. Giving such a system for a set of people who don't really understand what it is and how it can be used, is the real danger. They'll always use it to protect their interests.

Just imagine - What if Apple followed this Gartner 'Advice' from 2006 :)

Found that link to this service provider from this answer in Quora - http://www.quora.com/Hypothetical-Questions/Is-it-possible-f...

Beta = Shut down any day.

To set the context, I think Steve's post is more or less triggered by the Snarky comments that David's article got - http://www.wired.com/opinion/2013/02/the-end-of-the-web-comp...

"Psychic spies from china tries to hack your mind elation"

Changed the template, so that you can read it better :). Do Checkout

Alright dude, now check that again and buy me a beer ;)

Alright, 3 then ;)

I had my disclaimer, lol. As I already clarified some where else, these points are what I learned from what I was doing in the last few years, consulting for my customers modernizing their web sites/apps. And thanks for the advice, in fact I'm surviving pretty well ;)

Was talking about leveraging a suitable, existing library that follows a MV* pattern, not about creating your mygreatnextjsmv*.

About implementation - definitely depends on use cases. Anyway, learning them won't hurt anyway.

As there are lot of comments here, thought about clarifying few points in that article

1) About clean separation of concerns.

A lot of customers expect you to cleanly separate your client side javascript/css/artifacts from your server side implementation. Even to an extent where you can just take it and repackage the same with minor modifications using a container like Phonegap, and distribute it for mobile devices later. HTML5's significance is beyond web - it can take your app beyond the browser.

2) About the REST Layer

Anyway you are investing in building a web application, so you need to ensure the plumbing portion is re-usable beyond your traditional 'website'. If you want to build a native phone application or a Chrome plug in tomorrow, you should be able to use the same service layer.

Thank you for answering this for me. Even the trigger for this post was a series of interviews I did for .NET web developers in the last few weeks.

About JS MVC frameworks - It's about scaling your development teams by putting a re-usable pattern in place so that things will jell together.

HTML5 - My point was, understand the parts you can use now.

Optimization - Again, do it when you are ready to do it.

My blog is still on blogger, I havn't modified it much for the last few years, and the template is due for renewal as I put in the disclaimer towards the end of that article.

But the points I put forward is mostly what I practice these days, and the basis is the consulting experience I had from revamping the websites/web products across multiple domains for the customers I've worked for.

This IDE is here to stay,

I played with it much like clay,

There is a lot more to say,

But they may think I'm an array.

Made with love = Made not just for money, but Made for making the world a better place.

Quite impressive performance comparisons

I guess shutting down a service just like that with out providing a good exit path for the user is pretty bad. They slowly started killing the users one by one, by deteriorating the service more and more. Good work Google.

Coz it is Dec, and it is Google. ;)