Well it wasn't that bad to get to a usable state.
While you cant install packages directly from the IDE, or auto start the venv like you can Thonny, Spyder does let you specify a interpreter inside the environment, and if you start the environment first, it works correctly. But to get the python shell to work ( which is important )you have to install a few extra packages inside the environment, which is unfortunate. Means you cant use the native pipenv to create the dependencies list. But there are other ways to do that, so not end of world.
( and im sure some of you are saying, "well no kidding. this is basic stuff, idiot" but virtual environment is new to me, never really cared before, but been having some conflicting package issues lately so it was time to do it )
So, over the last week I got 3 of my softwares published in FreeBSD Ports, 2 days later one of them was built and added to the official package repo. Last night the other 2 were built and added to the official package repo.
https://www.freshports.org/textproc/hexcode/
https://www.freshports.org/security/diffcode/
https://www.freshports.org/security/rotate/
So ya, adding your own softwares to FreeBSD Ports is actually pretty easy. There's even a whole Pawbook for getting softwares published: https://docs.freebsd.org/en/books/porters-handbook/
2022-09-19 12:28 from LadySerenaKitty
So, over the last week I got 3 of my softwares published in FreeBSD
Ports, 2 days later one of them was built and added to the official
package repo. Last night the other 2 were built and added to the
official package repo.
https://www.freshports.org/textproc/hexcode/
https://www.freshports.org/security/diffcode/
https://www.freshports.org/security/rotate/
So ya, adding your own softwares to FreeBSD Ports is actually pretty
easy. There's even a whole Pawbook for getting softwares
published: https://docs.freebsd.org/en/books/porters-handbook/
Congratulations.
I am a regular packager for some Linux and BSD distributions. Some repositories are very relaxed about what they accept, while others are anal as heck "READ THE STYLE GUIDE, NOOB, WE USE TABS INSTEAD OF SPACE!!!!"
Tue Sep 20 2022 13:18:20 EDT from darknetuserCongratulations.
I am a regular packager for some Linux and BSD distributions. Some repositories are very relaxed about what they accept, while others are anal as heck "READ THE STYLE GUIDE, NOOB, WE USE TABS INSTEAD OF SPACE!!!!"
Ports does not care what coding style each third-party software uses. The actual code for my projects isn't in Ports, either, it's downloaded from GitLab. As far as the style guide for Ports goes, there are a few standards for the Makefile, but it's pretty open.
Ports does not care what coding style each third-party software
uses. The actual code for my projects isn't in Ports, either, it's
downloaded from GitLab. As far as the style guide for Ports goes,
there are a few standards for the Makefile, but it's pretty open.
Well, that was the point. SOme projects will fix your Makefile in order to make them fit the standard, and will tell you not to break it again. Some projects will have somebody rip your head off and command you to resubmit the whole thing lol
#GameChanger
2022-10-19 02:44 from IGnatius T Foobar <ajc@citadel.org>
I found out today that you can download an extension to Visual Studio
Code that makes it accept vi keybindings.
#GameChanger
You can also download gvim and it accepts vi keybindings out of the box.
The thing I didn't like about VS Code is that it has a traditional GUI editor in it. That was a deal breaker for me ... until I found out about the extension that adds vi keybindings. Now I've got my ultrawide screen set up with VS Code on the left half and a browser on the right half. As I develop a web application, the code tree is on screen, there is built in SSH and Git integration, the syntax coloring and suggestions work, but it still works like vi.
This is mind blowing. And remember, I am the most famous Microsoft hater you will ever meet.
The way it works just like vi is unbelievably complete. Commands like :wq! (or ZZ as I prefer) do "the right thing" -- in this case save the file and close the tab. Range substitution with a command like :1,$s/foo/bar works exactly as it should, performing the substitution all over the range, on screen, as you type it. cut/copy/paste with the yy, dd, and p/P commands even work between tabs.
And the whole thing can work over a single SSH connection if the machine you're sitting in front of is not the machine you're doing development on.
Multiple editor tabs and terminal tabs, all multiplexed over a single SSH connection. This works for me because I have a dedicated dev server that I connect to over SSH (which is kind of a requirement when you're developing an Internet-facing application).
How times have changed. Gates and Ballmer would never have allowed this kind of cross-platform openness to happen. VS Code is a freaking ELECTRON application and it runs everywhere.
Say what you will, vscode is very popular lately. Now that Java is Mostly Dead(TM), it might be the closest thing we have to an industry-standard IDE. It's lightweight and it's reasonably fast and full-featured enough for a lot of different languages.
socialism is popular today too, but that dont make it right :)
Only way id use it is if my job depended on it, and id be looking for a new job. ( and for me, spyder does quite nicely )
And I still vastly prefer Linux to Windows and look forward to the day when the silly dorks in IT finally allow us to run it on bare metal laptops again (I hear it's coming).
VS Code ... originally I couldn't get used to it because it uses modeless editing by default, which is what most people prefer. But once I found the vi keybindings extension ... it is awkward for me to say this but it's good, I like it, and I'm using it. It is open source and cross platform, which clearly contributed to its increasing ubiquity. So far I have done some work in C, JavaScript, Python, Markdown, and Terraform HCL. The only one that turned me off a little was Python, because the auto-completion-suggestions were a bit too aggressive. I would have to assume that can be turned down.
I'm not sure I'd call it "lightweight" unless you're comparing it to the old Visual Studio. It's an Electron app, after all.
I'm not sure I'd call it "lightweight" unless you're comparing it to
the old Visual Studio. It's an Electron app, after all.
It's lightweight and fast compared to IntelliJ.
2022-10-24 16:58 from Nurb432
socialism is popular today too, but that dont make it right :)
Look, I prefaced my comment with "say what you will", so THAT makes the following statement objectively right ;)
It's lightweight and fast compared to IntelliJ.
"Do you know what the J in Java stands for? It stands for SLOW!"
-- old 1990's proverb
Ya it was a tradeoff to be 'universal' ( more or less )
Thu Oct 27 2022 01:04:33 PM EDT from IGnatius T FoobarIt's lightweight and fast compared to IntelliJ.
"Do you know what the J in Java stands for? It stands for SLOW!"
-- old 1990's proverb
(I've spoken before about how the "Network Computing" concept was ahead of its time, so include that here by reference.)
What happened next was fascinating. Java's promise of becoming *the* way to write portable desktop applications faded, but as we all know, the language and its runtime environment did not die. Instead, Java ended up replacing Pascal as the preferred language for teaching computer science. And then, amazingly, Java ended up replacing COBOL as the lingua franca of business logic.
And so, while Java's original promise was fulfilled by web applications as browser technology evolved with XHR, DOM, HTML5, and fast JavaScript ... Java itself found its way into every enterprise back end, and for nearly two decades it became *the* language to learn if you wanted a boring 9-to-5 programming job at a bank or an insurance company. And so, just as we look into the back office and see those old mainframe folks today, in 20 years we will look into the back office and see those old Java folks.
(And no, I don't think "mainframes will always be here" as the pundits claim.
Look at any non-IBM mainframe environment -- Burroughs, for example -- it's being emulated on commodity hardware. IBM itself will not escape this fate.
They can claim their mainframes are still cool because they scribbled "CLOUD" on one with a crayon, but in the end this will be about as effective as making a TV commercial with nuns chatting with each other in Latin about how they read about OS/2 in Wired Magazine.)
Not sure Java ever really met its end goal, but it did try and all bashing aside, it was (is) usable and as you say, 'everywhere'. Sure it had issues ( what doesn't? ), but SUN did a good job trying to do the right thing. I also agree mainframes wont be here forever, but we have heard "they are dying" for 20 years.. and they are not gone yet.