#developmenttools — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #developmenttools, aggregated by home.social.
-
Google Fixes Antigravity Flaw That Enabled Code Execution
Google's Antigravity tool, designed to streamline coding, had a flaw that allowed hackers to run malicious code - but luckily, the tech giant has patched the vulnerability. This fix prevents cyber threats that could have exploited the tool's file-creation capabilities and lax input sanitization.
#CodeExecution #Antigravity #Google #Vulnerability #DevelopmentTools
-
One Open-source Project Daily
MacOS application to spoof / fake / mock your iOS / iPadOS or iPhoneSimulator device location. WatchOS and TvOS are partially supported.
https://github.com/Schlaubischlump/LocationSimulator
#1ospd #opensource #appkit #developmenttools #fake #fakelocations #iossimulator #iphonesimulator #ispoofer #libimobiledevice #location #locationspoof #locationspoofing #macos #mocklocation #mocklocations #navigation #simulation #spoof #swift -
One Open-source Project Daily
MacOS application to spoof / fake / mock your iOS / iPadOS or iPhoneSimulator device location. WatchOS and TvOS are partially supported.
https://github.com/Schlaubischlump/LocationSimulator
#1ospd #opensource #appkit #developmenttools #fake #fakelocations #iossimulator #iphonesimulator #ispoofer #libimobiledevice #location #locationspoof #locationspoofing #macos #mocklocation #mocklocations #navigation #simulation #spoof #swift -
One Open-source Project Daily
MacOS application to spoof / fake / mock your iOS / iPadOS or iPhoneSimulator device location. WatchOS and TvOS are partially supported.
https://github.com/Schlaubischlump/LocationSimulator
#1ospd #opensource #appkit #developmenttools #fake #fakelocations #iossimulator #iphonesimulator #ispoofer #libimobiledevice #location #locationspoof #locationspoofing #macos #mocklocation #mocklocations #navigation #simulation #spoof #swift -
One Open-source Project Daily
MacOS application to spoof / fake / mock your iOS / iPadOS or iPhoneSimulator device location. WatchOS and TvOS are partially supported.
https://github.com/Schlaubischlump/LocationSimulator
#1ospd #opensource #appkit #developmenttools #fake #fakelocations #iossimulator #iphonesimulator #ispoofer #libimobiledevice #location #locationspoof #locationspoofing #macos #mocklocation #mocklocations #navigation #simulation #spoof #swift -
One Open-source Project Daily
MacOS application to spoof / fake / mock your iOS / iPadOS or iPhoneSimulator device location. WatchOS and TvOS are partially supported.
https://github.com/Schlaubischlump/LocationSimulator
#1ospd #opensource #appkit #developmenttools #fake #fakelocations #iossimulator #iphonesimulator #ispoofer #libimobiledevice #location #locationspoof #locationspoofing #macos #mocklocation #mocklocations #navigation #simulation #spoof #swift -
https://winbuzzer.com/2026/02/03/github-major-service-outage-disrupts-developer-workflows-xcxwbn/
GitHub Suffers Major Outage Disrupting Dev Workflows
#GitHub #Developers #CloudServices #BigTech #DevelopmentTools #Microsoft
-
Công cụ mới giúp phiên bản và tra cứu kiến trúc phần mềm. Pacta cho phép tạo ảnh chụp kiến trúc, xem lịch sử và xu hướng, so sánh giữa các ảnh chụp và áp dụng quy tắc governace. #Pacta #KiếnTrúcPhầnMềm #PhátTriểnPhầnMềm #SoftwareArchitecture #DevelopmentTools
-
The Collapsing Cost of Software Development
The cost of generating software code is collapsing, and governments aren’t ready for what that means
If I could single out one trend from the past twelve months in software development for people in government to watch closely, it would be this.
AI coding assistants have reached a level of maturity that makes them a genuinely viable tool for developing and managing software systems – even large and complex ones.
Things are changing very fast, and it’s easy to get lost in the details, the lingo, and the hype. But the bottom line is really straightforward. AI tools are getting dramatically better at producing quality code, and software teams are gaining far greater control over that output. The cost of generating code is falling, and this trend is very likely to continue apace.
This matters for government because so many of the problems governments face with digital solutions trace back to how expensive software has been to build and maintain. That high cost is why legacy systems stay in service for decades. It shapes how governments recruit for technical roles. It drives how agencies structure contracts and write solicitations. It’s baked into assumptions that have guided technology decisions for years.
Those assumptions are about to be challenged.
As code generation becomes cheaper and more reliable, the knowledge premium will shift. What will matter most in the future is not the ability to write code, but the ability to understand and document how a system actually behaves. The government agencies that will succeed in this new world will be the ones that can clearly articulate what they need, verify that what they’ve built works correctly, and maintain a coherent understanding of their systems over time.
This shift will reshape how governments modernize their legacy systems, adopt new digital solutions, staff projects, and structure procurements. The impact will be significant – but only for governments that position themselves to take advantage of it.
That means creating space to experiment: internal labs to experiment with AI tools, pilot projects, partnerships with vendors who understand what these changes mean specifically for the public sector. And it means listening to people who have been paying close attention to this shift and can help translate it into actionable steps.
These changes are happening very, very fast and governments need to get ready for them. Right now.
#AI #artificialIntelligence #ChatGPT #Claude #DevelopmentTools
-
https://winbuzzer.com/2026/01/23/microsoft-launches-winapp-cli-for-windows-app-development-xcxwbn/
Microsoft Launches Winapp CLI for Windows App Development
#Microsoft #winapp #Windows #BigTech #OpenSource #AppDevelopment #DevelopmentTools #Packaging #MSIX #CLITools #DotNet #CPlusPlus #Rust #Electron #Business #Software
-
https://winbuzzer.com/2026/01/23/microsoft-launches-winapp-cli-for-windows-app-development-xcxwbn/
Microsoft Launches Winapp CLI for Windows App Development
#Microsoft #winapp #Windows #BigTech #OpenSource #AppDevelopment #DevelopmentTools #Packaging #MSIX #CLITools #DotNet #CPlusPlus #Rust #Electron #Business #Software
-
https://winbuzzer.com/2026/01/23/microsoft-launches-winapp-cli-for-windows-app-development-xcxwbn/
Microsoft Launches Winapp CLI for Windows App Development
#Microsoft #winapp #Windows #BigTech #OpenSource #AppDevelopment #DevelopmentTools #Packaging #MSIX #CLITools #DotNet #CPlusPlus #Rust #Electron #Business #Software
-
https://winbuzzer.com/2026/01/23/microsoft-launches-winapp-cli-for-windows-app-development-xcxwbn/
Microsoft Launches Winapp CLI for Windows App Development
#Microsoft #winapp #Windows #BigTech #OpenSource #AppDevelopment #DevelopmentTools #Packaging #MSIX #CLITools #DotNet #CPlusPlus #Rust #Electron #Business #Software
-
https://winbuzzer.com/2026/01/23/microsoft-launches-winapp-cli-for-windows-app-development-xcxwbn/
Microsoft Launches Winapp CLI for Windows App Development
#Microsoft #winapp #Windows #BigTech #OpenSource #AppDevelopment #DevelopmentTools #Packaging #MSIX #CLITools #DotNet #CPlusPlus #Rust #Electron #Business #Software
-
Amazon pushes in-house AI coding tool Kiro over competitors’, memo shows
By Greg Bensinger SAN FRANCISCO (Reuters) -Amazon suggested its engineers eschew AI code generation tools from third-party companies…
#NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Artificialintelligence #AI #Amazon #ArtificialIntelligence #ClaudeCode #developmenttools #internalguidance #internalmemo #Technology
https://www.newsbeep.com/us/312230/ -
Amazon pushes in-house AI coding tool Kiro over competitors’, memo shows
By Greg Bensinger SAN FRANCISCO (Reuters) -Amazon suggested its engineers eschew AI code generation tools from third-party companies…
#NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Artificialintelligence #AI #Amazon #ArtificialIntelligence #ClaudeCode #developmenttools #internalguidance #internalmemo #Technology
https://www.newsbeep.com/us/312230/ -
Worm flooding npm registry with token stealers still isn’t under control https://www.csoonline.com/article/4090568/worm-flooding-npm-registry-with-token-stealers-still-isnt-under-control-2.html #ApplicationSecurity #SoftwareDevelopment #DevelopmentTools #OpenSource #Security
-
Ra mắt Wirebrowser, ứng dụng mã nguồn mở trên desktop kết hợp chặn HTTP, phát lại API, kiểm tra bộ nhớ trình duyệt và thu thập API - được hỗ trợ bởi Chrome DevTools Protocol. #Wirebrowser #HTTP #API #ChromeDevTools #MãNguồnMở #OpenSource #CôngCụPhátTriển #DevelopmentTools
-
via @dotnet : Getting Started with the Aspire CLI
https://ift.tt/u51y8Vz
#AspireCLI #DotNet #DevelopmentTools #Microservices #ApplicationDevelopment #CrossPlatform #SoftwareEngineering #DevOps #Programming #WebDevelopment #CloudIntegration #OpenSource #TechTutor… -
I built a tiny mac app to monitor and manage my development processes
https://github.com/kagehq/port-kill
#HackerNews #tinyMacApp #developmentTools #processManagement #GitHub #codingCommunity
-
I built a tiny mac app to monitor and manage my development processes
https://github.com/kagehq/port-kill
#HackerNews #tinyMacApp #developmentTools #processManagement #GitHub #codingCommunity
-
I built a tiny mac app to monitor and manage my development processes
https://github.com/kagehq/port-kill
#HackerNews #tinyMacApp #developmentTools #processManagement #GitHub #codingCommunity
-
I built a tiny mac app to monitor and manage my development processes
https://github.com/kagehq/port-kill
#HackerNews #tinyMacApp #developmentTools #processManagement #GitHub #codingCommunity
-
I built a tiny mac app to monitor and manage my development processes
https://github.com/kagehq/port-kill
#HackerNews #tinyMacApp #developmentTools #processManagement #GitHub #codingCommunity
-
via @dotnet : Announcing the NuGet MCP Server Preview
https://ift.tt/QbdgEc8
#NuGet #MCPServer #DotNet #AI #PackageManagement #RealTimeIntegration #DevelopmentTools #DependencyManagement #OpenStandard #MicrosoftResearch #PreviewRelease #Feedback #CodingAgent #Vi… -
via @dotnet : Announcing the NuGet MCP Server Preview
https://ift.tt/QbdgEc8
#NuGet #MCPServer #DotNet #AI #PackageManagement #RealTimeIntegration #DevelopmentTools #DependencyManagement #OpenStandard #MicrosoftResearch #PreviewRelease #Feedback #CodingAgent #Vi… -
The risks of entry-level developers over relying on AI – Source: www.csoonline.com https://ciso2ciso.com/the-risks-of-entry-level-developers-over-relying-on-ai-source-www-csoonline-com/ #rssfeedpostgeneratorecho #CyberSecurityNews #DevelopmentTools #GenerativeAI #CSOonline #CSOOnline #itskills
-
The risks of entry-level developers over relying on AI https://www.csoonline.com/article/3951403/the-risks-of-entry-level-developers-over-relying-on-ai.html #DevelopmentTools #GenerativeAI #ITSkills
-
> file versioning
optionally :)
I'd add networked file system, though it hides in "virtual devices". And integrated debugger (DDT).
But the big, underappreciared thing about the ITS operating system (OS), too easily seen as a weakness, was the LACK of security.
Today, security is essential. But the luxury of working WITHOUT it back then was a HUGE productivity gain.
ITS existed on the ARPANET for YEARS with NO file security, NO protection against ANY user (even not logged in users) shutting down timesharing, tools that let ANY user spy on any other, and commands to read interactive messages or email that took a command line argument of WHOSE to read. Yet abuse was negligible/tolerable for a LONG time.
Partly an artifact of the time. Some combination of (1) most folks not thinking to make mischief, (2) most users knowing how precious it was and being asked to behave like adults and respect it, (3) using those same tools to see what others were doing and mutually policing, (4) using spy tools to make sure people weren't floundering and frustrated but helped to succeed, (5) treating even guests (tourists) with respect, (6) "security through obscurity" still worked back then.
I didn't understand how critical this was until I started using a Digital Equpment Corporation (DEC) commercial TOPS-20 OS on basically the same (PDP-10) hardware. I felt suddenly WAY less productive and was at a loss for why. I went back to an ITS host and enumerated all the programs in the system directories (SYS, SYS1, SYS2, SYS3) to see what was missing.
One realization was that most of that software just supported other ITS software. It wasn't what was missing.
The other realization, something I then had no name for but with benefit of history I now do, was that ITS was an early form of social media--a better, less nutty way to perceive its spying capabilities--like a DDT (shell) command ("os", for Output Spy) to say WHOSE console to spy on.
Like in Star Trek TNG episode "I, Borg", TOPS-20 made me feel like Hugh did: I couldn't "hear the voices" of other users. (Metaphorically hear. We mostly had no audio back then.) The difference from ITS? I was lonely. I could send messages, but only private ones. Socializing information, knowing what others were doing, sharing work? All hard. The silence was deafening.
Why WOULD anyone be allowed to see somebody else's screen? Why would that EVER not be creepy? Why would someone WANT you to read their messages to/from others?
Isn't that what we do on Facebook? Somebody starts a conversation and others arrive to see it, see what's been said so far, and add to it. That's how ITS felt. You'd login, notice friends were online, read their recent messages to find out what was going on, and then (once caught up in conversations), join in. Details were different, but in the social media paradigm it's easier to see why it felt not so much creepy as fabulously useful, especially compared to the isolation of other OSes of the time (and now). It made us enormously more efficient.
And the ability to watch somebody else's screen? We do it in zoom today, though we now elect when we do it and when we can't. Still, powerful. People imagine it was more primitive back then, and it was. But different too. No camera, just screen, but no ability to opt out of sharing it. Not really the screen, the output buffer (kinda like a low-level, ephemeral event queue). Often it looked crappy on a slow terminal trying to watch a fast one because of data loss trying to keep up, or trying to watch a screen with sophisticated display capability from a screen (or even "paper terminal") lacking such capability. Even so, it worked pretty well.
It was ALSO an early interactive, collaborative development environment. Programmers worked with each other AND users (who they could watch). We didn't lack ideas. A lot of today's "new inventions" may be things we knew we wanted. We were limited by what tools were implemented, so progress started slow. Processors were slower. But people were clever, and much more careful with time/space efficiency than today.
I recall Emacs starting in about 3 seconds on ITS, on a PDP-10 with 10-15 users, slower if 30. Today, on MUCH faster personal hardware, it starts fast but still not instantly. More happens now under the covers. More flexibility AND sloppiness are allowed.
Back then if something didn't work, you sent a bug report. Someone might say "show me". So you'd do it on your console and assume they could watch. Like zoom (sans video).
Most stuff lacked documentation but people just typed queries to command line (like copilot?). It'd say syntax error but often someone spying would volunteer an answer, maybe before the user asked. :)
We built many sketches of our imagined futures. ITS was all about that in a way other OSes of the time were not.
#DEC #TOPS20 #ITS #TechHistory #history #tech #SocialMedia #collaboration #DevelopmentTools #programming #security #sharing
-
> file versioning
optionally :)
I'd add networked file system, though it hides in "virtual devices". And integrated debugger (DDT).
But the big, underappreciared thing about the ITS operating system (OS), too easily seen as a weakness, was the LACK of security.
Today, security is essential. But the luxury of working WITHOUT it back then was a HUGE productivity gain.
ITS existed on the ARPANET for YEARS with NO file security, NO protection against ANY user (even not logged in users) shutting down timesharing, tools that let ANY user spy on any other, and commands to read interactive messages or email that took a command line argument of WHOSE to read. Yet abuse was negligible/tolerable for a LONG time.
Partly an artifact of the time. Some combination of (1) most folks not thinking to make mischief, (2) most users knowing how precious it was and being asked to behave like adults and respect it, (3) using those same tools to see what others were doing and mutually policing, (4) using spy tools to make sure people weren't floundering and frustrated but helped to succeed, (5) treating even guests (tourists) with respect, (6) "security through obscurity" still worked back then.
I didn't understand how critical this was until I started using a Digital Equpment Corporation (DEC) commercial TOPS-20 OS on basically the same (PDP-10) hardware. I felt suddenly WAY less productive and was at a loss for why. I went back to an ITS host and enumerated all the programs in the system directories (SYS, SYS1, SYS2, SYS3) to see what was missing.
One realization was that most of that software just supported other ITS software. It wasn't what was missing.
The other realization, something I then had no name for but with benefit of history I now do, was that ITS was an early form of social media--a better, less nutty way to perceive its spying capabilities--like a DDT (shell) command ("os", for Output Spy) to say WHOSE console to spy on.
Like in Star Trek TNG episode "I, Borg", TOPS-20 made me feel like Hugh did: I couldn't "hear the voices" of other users. (Metaphorically hear. We mostly had no audio back then.) The difference from ITS? I was lonely. I could send messages, but only private ones. Socializing information, knowing what others were doing, sharing work? All hard. The silence was deafening.
Why WOULD anyone be allowed to see somebody else's screen? Why would that EVER not be creepy? Why would someone WANT you to read their messages to/from others?
Isn't that what we do on Facebook? Somebody starts a conversation and others arrive to see it, see what's been said so far, and add to it. That's how ITS felt. You'd login, notice friends were online, read their recent messages to find out what was going on, and then (once caught up in conversations), join in. Details were different, but in the social media paradigm it's easier to see why it felt not so much creepy as fabulously useful, especially compared to the isolation of other OSes of the time (and now). It made us enormously more efficient.
And the ability to watch somebody else's screen? We do it in zoom today, though we now elect when we do it and when we can't. Still, powerful. People imagine it was more primitive back then, and it was. But different too. No camera, just screen, but no ability to opt out of sharing it. Not really the screen, the output buffer (kinda like a low-level, ephemeral event queue). Often it looked crappy on a slow terminal trying to watch a fast one because of data loss trying to keep up, or trying to watch a screen with sophisticated display capability from a screen (or even "paper terminal") lacking such capability. Even so, it worked pretty well.
It was ALSO an early interactive, collaborative development environment. Programmers worked with each other AND users (who they could watch). We didn't lack ideas. A lot of today's "new inventions" may be things we knew we wanted. We were limited by what tools were implemented, so progress started slow. Processors were slower. But people were clever, and much more careful with time/space efficiency than today.
I recall Emacs starting in about 3 seconds on ITS, on a PDP-10 with 10-15 users, slower if 30. Today, on MUCH faster personal hardware, it starts fast but still not instantly. More happens now under the covers. More flexibility AND sloppiness are allowed.
Back then if something didn't work, you sent a bug report. Someone might say "show me". So you'd do it on your console and assume they could watch. Like zoom (sans video).
Most stuff lacked documentation but people just typed queries to command line (like copilot?). It'd say syntax error but often someone spying would volunteer an answer, maybe before the user asked. :)
We built many sketches of our imagined futures. ITS was all about that in a way other OSes of the time were not.
#DEC #TOPS20 #ITS #TechHistory #history #tech #SocialMedia #collaboration #DevelopmentTools #programming #security #sharing
-
> file versioning
optionally :)
I'd add networked file system, though it hides in "virtual devices". And integrated debugger (DDT).
But the big, underappreciared thing about the ITS operating system (OS), too easily seen as a weakness, was the LACK of security.
Today, security is essential. But the luxury of working WITHOUT it back then was a HUGE productivity gain.
ITS existed on the ARPANET for YEARS with NO file security, NO protection against ANY user (even not logged in users) shutting down timesharing, tools that let ANY user spy on any other, and commands to read interactive messages or email that took a command line argument of WHOSE to read. Yet abuse was negligible/tolerable for a LONG time.
Partly an artifact of the time. Some combination of (1) most folks not thinking to make mischief, (2) most users knowing how precious it was and being asked to behave like adults and respect it, (3) using those same tools to see what others were doing and mutually policing, (4) using spy tools to make sure people weren't floundering and frustrated but helped to succeed, (5) treating even guests (tourists) with respect, (6) "security through obscurity" still worked back then.
I didn't understand how critical this was until I started using a Digital Equpment Corporation (DEC) commercial TOPS-20 OS on basically the same (PDP-10) hardware. I felt suddenly WAY less productive and was at a loss for why. I went back to an ITS host and enumerated all the programs in the system directories (SYS, SYS1, SYS2, SYS3) to see what was missing.
One realization was that most of that software just supported other ITS software. It wasn't what was missing.
The other realization, something I then had no name for but with benefit of history I now do, was that ITS was an early form of social media--a better, less nutty way to perceive its spying capabilities--like a DDT (shell) command ("os", for Output Spy) to say WHOSE console to spy on.
Like in Star Trek TNG episode "I, Borg", TOPS-20 made me feel like Hugh did: I couldn't "hear the voices" of other users. (Metaphorically hear. We mostly had no audio back then.) The difference from ITS? I was lonely. I could send messages, but only private ones. Socializing information, knowing what others were doing, sharing work? All hard. The silence was deafening.
Why WOULD anyone be allowed to see somebody else's screen? Why would that EVER not be creepy? Why would someone WANT you to read their messages to/from others?
Isn't that what we do on Facebook? Somebody starts a conversation and others arrive to see it, see what's been said so far, and add to it. That's how ITS felt. You'd login, notice friends were online, read their recent messages to find out what was going on, and then (once caught up in conversations), join in. Details were different, but in the social media paradigm it's easier to see why it felt not so much creepy as fabulously useful, especially compared to the isolation of other OSes of the time (and now). It made us enormously more efficient.
And the ability to watch somebody else's screen? We do it in zoom today, though we now elect when we do it and when we can't. Still, powerful. People imagine it was more primitive back then, and it was. But different too. No camera, just screen, but no ability to opt out of sharing it. Not really the screen, the output buffer (kinda like a low-level, ephemeral event queue). Often it looked crappy on a slow terminal trying to watch a fast one because of data loss trying to keep up, or trying to watch a screen with sophisticated display capability from a screen (or even "paper terminal") lacking such capability. Even so, it worked pretty well.
It was ALSO an early interactive, collaborative development environment. Programmers worked with each other AND users (who they could watch). We didn't lack ideas. A lot of today's "new inventions" may be things we knew we wanted. We were limited by what tools were implemented, so progress started slow. Processors were slower. But people were clever, and much more careful with time/space efficiency than today.
I recall Emacs starting in about 3 seconds on ITS, on a PDP-10 with 10-15 users, slower if 30. Today, on MUCH faster personal hardware, it starts fast but still not instantly. More happens now under the covers. More flexibility AND sloppiness are allowed.
Back then if something didn't work, you sent a bug report. Someone might say "show me". So you'd do it on your console and assume they could watch. Like zoom (sans video).
Most stuff lacked documentation but people just typed queries to command line (like copilot?). It'd say syntax error but often someone spying would volunteer an answer, maybe before the user asked. :)
We built many sketches of our imagined futures. ITS was all about that in a way other OSes of the time were not.
#DEC #TOPS20 #ITS #TechHistory #history #tech #SocialMedia #collaboration #DevelopmentTools #programming #security #sharing
-
> file versioning
optionally :)
I'd add networked file system, though it hides in "virtual devices". And integrated debugger (DDT).
But the big, underappreciared thing about the ITS operating system (OS), too easily seen as a weakness, was the LACK of security.
Today, security is essential. But the luxury of working WITHOUT it back then was a HUGE productivity gain.
ITS existed on the ARPANET for YEARS with NO file security, NO protection against ANY user (even not logged in users) shutting down timesharing, tools that let ANY user spy on any other, and commands to read interactive messages or email that took a command line argument of WHOSE to read. Yet abuse was negligible/tolerable for a LONG time.
Partly an artifact of the time. Some combination of (1) most folks not thinking to make mischief, (2) most users knowing how precious it was and being asked to behave like adults and respect it, (3) using those same tools to see what others were doing and mutually policing, (4) using spy tools to make sure people weren't floundering and frustrated but helped to succeed, (5) treating even guests (tourists) with respect, (6) "security through obscurity" still worked back then.
I didn't understand how critical this was until I started using a Digital Equpment Corporation (DEC) commercial TOPS-20 OS on basically the same (PDP-10) hardware. I felt suddenly WAY less productive and was at a loss for why. I went back to an ITS host and enumerated all the programs in the system directories (SYS, SYS1, SYS2, SYS3) to see what was missing.
One realization was that most of that software just supported other ITS software. It wasn't what was missing.
The other realization, something I then had no name for but with benefit of history I now do, was that ITS was an early form of social media--a better, less nutty way to perceive its spying capabilities--like a DDT (shell) command ("os", for Output Spy) to say WHOSE console to spy on.
Like in Star Trek TNG episode "I, Borg", TOPS-20 made me feel like Hugh did: I couldn't "hear the voices" of other users. (Metaphorically hear. We mostly had no audio back then.) The difference from ITS? I was lonely. I could send messages, but only private ones. Socializing information, knowing what others were doing, sharing work? All hard. The silence was deafening.
Why WOULD anyone be allowed to see somebody else's screen? Why would that EVER not be creepy? Why would someone WANT you to read their messages to/from others?
Isn't that what we do on Facebook? Somebody starts a conversation and others arrive to see it, see what's been said so far, and add to it. That's how ITS felt. You'd login, notice friends were online, read their recent messages to find out what was going on, and then (once caught up in conversations), join in. Details were different, but in the social media paradigm it's easier to see why it felt not so much creepy as fabulously useful, especially compared to the isolation of other OSes of the time (and now). It made us enormously more efficient.
And the ability to watch somebody else's screen? We do it in zoom today, though we now elect when we do it and when we can't. Still, powerful. People imagine it was more primitive back then, and it was. But different too. No camera, just screen, but no ability to opt out of sharing it. Not really the screen, the output buffer (kinda like a low-level, ephemeral event queue). Often it looked crappy on a slow terminal trying to watch a fast one because of data loss trying to keep up, or trying to watch a screen with sophisticated display capability from a screen (or even "paper terminal") lacking such capability. Even so, it worked pretty well.
It was ALSO an early interactive, collaborative development environment. Programmers worked with each other AND users (who they could watch). We didn't lack ideas. A lot of today's "new inventions" may be things we knew we wanted. We were limited by what tools were implemented, so progress started slow. Processors were slower. But people were clever, and much more careful with time/space efficiency than today.
I recall Emacs starting in about 3 seconds on ITS, on a PDP-10 with 10-15 users, slower if 30. Today, on MUCH faster personal hardware, it starts fast but still not instantly. More happens now under the covers. More flexibility AND sloppiness are allowed.
Back then if something didn't work, you sent a bug report. Someone might say "show me". So you'd do it on your console and assume they could watch. Like zoom (sans video).
Most stuff lacked documentation but people just typed queries to command line (like copilot?). It'd say syntax error but often someone spying would volunteer an answer, maybe before the user asked. :)
We built many sketches of our imagined futures. ITS was all about that in a way other OSes of the time were not.
#DEC #TOPS20 #ITS #TechHistory #history #tech #SocialMedia #collaboration #DevelopmentTools #programming #security #sharing
-
> file versioning
optionally :)
I'd add networked file system, though it hides in "virtual devices". And integrated debugger (DDT).
But the big, underappreciared thing about the ITS operating system (OS), too easily seen as a weakness, was the LACK of security.
Today, security is essential. But the luxury of working WITHOUT it back then was a HUGE productivity gain.
ITS existed on the ARPANET for YEARS with NO file security, NO protection against ANY user (even not logged in users) shutting down timesharing, tools that let ANY user spy on any other, and commands to read interactive messages or email that took a command line argument of WHOSE to read. Yet abuse was negligible/tolerable for a LONG time.
Partly an artifact of the time. Some combination of (1) most folks not thinking to make mischief, (2) most users knowing how precious it was and being asked to behave like adults and respect it, (3) using those same tools to see what others were doing and mutually policing, (4) using spy tools to make sure people weren't floundering and frustrated but helped to succeed, (5) treating even guests (tourists) with respect, (6) "security through obscurity" still worked back then.
I didn't understand how critical this was until I started using a Digital Equpment Corporation (DEC) commercial TOPS-20 OS on basically the same (PDP-10) hardware. I felt suddenly WAY less productive and was at a loss for why. I went back to an ITS host and enumerated all the programs in the system directories (SYS, SYS1, SYS2, SYS3) to see what was missing.
One realization was that most of that software just supported other ITS software. It wasn't what was missing.
The other realization, something I then had no name for but with benefit of history I now do, was that ITS was an early form of social media--a better, less nutty way to perceive its spying capabilities--like a DDT (shell) command ("os", for Output Spy) to say WHOSE console to spy on.
Like in Star Trek TNG episode "I, Borg", TOPS-20 made me feel like Hugh did: I couldn't "hear the voices" of other users. (Metaphorically hear. We mostly had no audio back then.) The difference from ITS? I was lonely. I could send messages, but only private ones. Socializing information, knowing what others were doing, sharing work? All hard. The silence was deafening.
Why WOULD anyone be allowed to see somebody else's screen? Why would that EVER not be creepy? Why would someone WANT you to read their messages to/from others?
Isn't that what we do on Facebook? Somebody starts a conversation and others arrive to see it, see what's been said so far, and add to it. That's how ITS felt. You'd login, notice friends were online, read their recent messages to find out what was going on, and then (once caught up in conversations), join in. Details were different, but in the social media paradigm it's easier to see why it felt not so much creepy as fabulously useful, especially compared to the isolation of other OSes of the time (and now). It made us enormously more efficient.
And the ability to watch somebody else's screen? We do it in zoom today, though we now elect when we do it and when we can't. Still, powerful. People imagine it was more primitive back then, and it was. But different too. No camera, just screen, but no ability to opt out of sharing it. Not really the screen, the output buffer (kinda like a low-level, ephemeral event queue). Often it looked crappy on a slow terminal trying to watch a fast one because of data loss trying to keep up, or trying to watch a screen with sophisticated display capability from a screen (or even "paper terminal") lacking such capability. Even so, it worked pretty well.
It was ALSO an early interactive, collaborative development environment. Programmers worked with each other AND users (who they could watch). We didn't lack ideas. A lot of today's "new inventions" may be things we knew we wanted. We were limited by what tools were implemented, so progress started slow. Processors were slower. But people were clever, and much more careful with time/space efficiency than today.
I recall Emacs starting in about 3 seconds on ITS, on a PDP-10 with 10-15 users, slower if 30. Today, on MUCH faster personal hardware, it starts fast but still not instantly. More happens now under the covers. More flexibility AND sloppiness are allowed.
Back then if something didn't work, you sent a bug report. Someone might say "show me". So you'd do it on your console and assume they could watch. Like zoom (sans video).
Most stuff lacked documentation but people just typed queries to command line (like copilot?). It'd say syntax error but often someone spying would volunteer an answer, maybe before the user asked. :)
We built many sketches of our imagined futures. ITS was all about that in a way other OSes of the time were not.
#DEC #TOPS20 #ITS #TechHistory #history #tech #SocialMedia #collaboration #DevelopmentTools #programming #security #sharing
-
CocoaPods flaws left iOS, macOS apps open to supply-chain attack https://www.csoonline.com/article/2512935/cocoapods-flaws-left-ios-macos-apps-open-to-supply-chain-attack.html #DevelopmentLibrariesandFrameworks #DevelopmentTools #MacOSSecurity #iOSSecurity
-
Maker of RStudio launches new R and Python IDE - The company best known for RStudio, the leading integrated development environment (ID... - https://www.infoworld.com/article/3715702/maker-of-rstudio-launches-new-r-and-python-ide.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #datascience #rlanguage #analytics #python
-
Maker of RStudio launches new R and Python IDE - The company best known for RStudio, the leading integrated development environment (ID... - https://www.infoworld.com/article/3715702/maker-of-rstudio-launches-new-r-and-python-ide.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #datascience #rlanguage #analytics #python
-
Maker of RStudio launches new R and Python IDE - The company best known for RStudio, the leading integrated development environment (ID... - https://www.infoworld.com/article/3715702/maker-of-rstudio-launches-new-r-and-python-ide.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #datascience #rlanguage #analytics #python
-
Maker of RStudio launches new R and Python IDE - The company best known for RStudio, the leading integrated development environment (ID... - https://www.infoworld.com/article/3715702/maker-of-rstudio-launches-new-r-and-python-ide.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #datascience #rlanguage #analytics #python
-
Maker of RStudio launches new R and Python IDE - The company best known for RStudio, the leading integrated development environment (ID... - https://www.infoworld.com/article/3715702/maker-of-rstudio-launches-new-r-and-python-ide.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #datascience #rlanguage #analytics #python
-
JetBrains AI Assistant to integrate Google Gemini AI models - JetBrains plans to use the Google Cloud Vertex AI development platform to bring Google... - https://www.infoworld.com/article/3715624/jetbrains-ai-assistant-to-integrate-google-gemini-ai-models.html#tk.rss_all #integrateddevelopmentenvironments #artificialintelligence #softwaredevelopment #developmenttools #generativeai
-
LlamaIndex review: Easy context-augmented LLM applications - “Turn your enterprise data into production-ready LLM applications,” blares the LlamaIn... - https://www.infoworld.com/article/3715622/llamaindex-review-easy-context-augmented-llm-applications.html#tk.rss_all #developmentlibrariesandframeworks #artificialintelligence #softwaredevelopment #developmenttools #cloudcomputing #generativeai
-
Apple’s Xcode 16 adds AI-powered code completion - Apple has released a beta version of Xcode 16, an update to the integrated development... - https://www.infoworld.com/article/3715580/apples-xcode-16-adds-ai-powered-code-completion.html#tk.rss_all #integrateddevelopmentenvironments #artificialintelligence #softwaredevelopment #developmenttools #generativeai #swift #apple
-
Visual Studio Code adds multiple tabs selection - With Visual Studio Code 1.90, otherwise known as the May 2024 release of the editor, M... - https://www.infoworld.com/article/3715357/visual-studio-code-adds-multiple-tabs-selection.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #visualstudiocode #developmenttools
-
Visual Studio rolls out new Extension Manager - Microsoft now is including its updated Extension Manager for Visual Studio as an on-by... - https://www.infoworld.com/article/3715353/visual-studio-rolls-out-new-extension-manager.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #visualstudio
-
JetBrains releases RustRover IDE for Rust development - JetBrains has released RustRover, a dedicated IDE for the Rust programming language th... - https://www.infoworld.com/article/3715317/jetbrains-releases-rustrover-ide-for-rust-development.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #rust
-
Architecting flexible back ends with GraphQL - As businesses traverse the complexities of the digital landscape, the seamless integra... - https://www.infoworld.com/article/3715487/architecting-flexible-back-ends-with-graphql.html#tk.rss_all #developmentlibrariesandframeworks #programminglanguages #softwaredevelopment #developmenttools #apis
-
JetBrains releases Aqua IDE for test automation - JetBrains has announced the official public release of Aqua, an IDE explicitly designe... - https://www.infoworld.com/article/3715269/jetbrains-releases-aqua-ide-for-test-automation.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools #apptesting
-
JetBrains launches IDE management suite - JetBrains has introduced JetBrains IDE Services, a product suite intended to simplify ... - https://www.infoworld.com/article/3715320/jetbrains-launches-ide-management-suite.html#tk.rss_all #integrateddevelopmentenvironments #softwaredevelopment #developmenttools
-
Visual Studio update brings smoother Copilot integration - With the third preview of the planned Visual Studio 2022 17.10, Microsoft has “unified... - https://www.infoworld.com/article/3715220/visual-studio-update-brings-smoother-copilot-integration.html#tk.rss_all #integrateddevelopmentenvironments #artificialintelligence #softwaredevelopment #developmenttools #visualstudio #generativeai
-
Gemini Code Assist debuts at Google Cloud Next 24 - Google’s cloud computing division, Google Cloud, has changed the name of its previousl... - https://www.infoworld.com/article/3715120/gemini-code-assist-debuts-at-google-cloud-next-24.html#tk.rss_all #artificialintelligence #softwaredevelopment #googlecloudplatform #developmenttools #cloudcomputing #generativeai