2,104 karma · joined March 2, 2016
github: https://github.com/spapas
meet.hn/city/gr-Athens
I didn't know about picocrypt but I already have two options for safely encrypting files: 7zip with its AES-256 (simple) and veracrypt with various algorithms (more involved but allows you to mount the encrypted vols). Actually these are already mentioned in the tool's readmy, great work: https://github.com/Picocrypt/Picocrypt?tab=readme-ov-file#co...
Do you know if there's a similar solution for vscode?
Also male perfume nowadays is either too weak or too sweet (or too expensive if you go the niche route). So either I'll wear a perfume that will smell for 30 minutes and nobody will notice or I'll bite the bullet and wear a club perfume that will suffocate people (and not even smell good).
I would definitely use it but the main disadvantage is that some keybindings work differently than vim. I understand that the keybindings may be better that the vim ones but after years of using vim I expect "x" in normal mode to delete the character under the cursor or "d" to wait for the motion before deleting anything. When this does not happen I get confused and angry. I think this would be a problem with most people that are using vim; it's very difficult to change your habits especially since you can't ever escape from vim because of its ubiquity.
Thankfully, some good people have released evil-helix, a soft fork of Helix which introduces Vim keybindings https://github.com/usagi-flow/evil-helix ; I tried it and it works great so I'll totally recommend it to people that have my problems.
As a final notice, helix (and evil-helix) works great in Windows (cmd). No need to install rust or anything. Get the .exe and you're gtg.
Django has a lot of beloved features but I think one of the most important is it's stability through the years: I actually have production apps that started on Django 1.4 and python 2.6 and now are updated and with with Django 5 and python 3.13.
All this without too much effort on my side or paying companies to support my projects.
So thank you Django people for the hard work!
Would it be possible for the moderators to penalize such articles so they can't easily gain traction similar to articles about politics?
A. Was playable on mobile
B. Could use the phone's gyroscope for controlling the ball
However I really like installing uv globally on my Windows systems and then using uvx to run stuff without caring about venvs and putting stuff to path.
Very good controllers and firm design. Great value for its price!
Unfortunately it's not that good on postgres or ms sql server. Feels more buggy and slow for these databases but I'm not sure if it's Heidi or the db drivers.
I'm also one of the people that used heidi on Linux with wine (along with notepad++) so a native version is more than welcome!
> For free models, rate limits are determined by the credits that you have purchased. If you have purchased at least 10 credits, your free model rate limit will be 1000 requests per day. Otherwise, you will be rate limited to 50 free model API requests per day.
Lazarus should have been the golden standard for creating desktop apps. Every other solution I've tried is subpar either in licensing or costs in general, executable size and resource usage, non native components, extra dependencies etc
The main advantage of office 2003 of course is that it's the last office without activation and other crap: you pass the serial and own it for life, it won't bother you again.
I wantwd to only use 2003 but after the 10th time I argued with a person that sent me a docx for editing I gave up.
Everything, and I mean everything is already either in core Django or in a great and properly supported django package that's been used in years and has been proven to be reliable.
I really can't understand the purpose of this package. Taking a peek at the about as mentioned by some others:
> You can think of Plain as a "what if?" > What if you didn't have to worry about deprecation policies?
The fact that Django has deprecation policies and they are so religiously followed allows me (and others) to have 10+ years old projects running in Django 5.1 and being ready for 5.2 without any problems or baggage!
> What if there were no committees?
A committee is a good thing. It ensures two things: a. It's not possible to commercialize the project. b. It makes sure that it will do what's best for most users. Some decisions may no be good for a particular user but it would be best for most users (considering my previous comment; I want to keep my 10+ years old project properly supported).
> What if you could change anything without consequence?
See previous comments. You can change anything without consequence when you have a clean slate, not when you need to support current stuff.
> What if Django wasn't originally built for a newspaper circa 2003?
This really doesn't relevant. Django is a general purpose framework.
> What if you had a clean slate, but a proven head start?
See the previous comments.
> working through years of incremental progress and committees, with a very real possibility of some things never happening, is just not for me.
Please see my previous answers. Also, about changing stuff, that's the purpose of packages, ain't it? Django has a lot of escape hatches to change its behavior from the defaults. And of course if you wanted to do something not supported you could try to do a PR so as to open another escape hatch so Django will keep the default behavior but you'll be able to implement your thingie.
Concluding, I really don't like this project forking Django because all this effort could be put to better use and definitely not try to split the community. Especially the community of a real Open Source project like Django.
> Signal stated already that they would sooner exit certain markets than violate their security
You still need to rely on a third party's goodwill to keep that promise. Also even if they are willing to keep the promise it is possible that they won't be able.
The fact is that Red Hat killed centos a little after it was acquired by IBM. Who decided this is not something that we'll learn (or even care anyway).
The fact that this could have been possible is the reason why the pgp/gpg way (you manage your certificate and you choose whose certificates to trust) is still the only way to have true encrypted communications.
Using centralised services to encrypt important data is a joke.
What kind of "team" is this, where nobody has 5 minutes to merge? Are they robots or they are mocking us?
We have a 10+ years old desktop project (.exe) in C# that uses MS SQL Server as a Database and we need to change it to be a proper web-app. We are heavy Django users and now we have stumbled upon a wall. Unfortunately because of the complexity of the project it's not feasible to change the DB.