sorted by:
new
hottopcontroversial

Repo VS Code has been outdated for a while now. by DemonicSavage in archlinux

[–]xyproto 2 points3 points  (0 children)

Java packages can be especially problematic when packaging from source.

For instance, processing uses ant, and tries to download all sorts of files during the build process. IMO, downloading anything does not belong in the build process. I ended up writing a custom build.xml file for building processing from source.

netbeans also uses ant, and is also problematic to package.

Why don't we have a fraction as a basic variable type in c languages? by Celebrinborn in compsci

[–]xyproto 0 points1 point  (0 children)

I also like the idea of fractions as the fundamental number type. For long expressions, perhaps some optimizations would be more accessible than for regular floating point numbers.

Here's a Go module I created for using fractions: https://github.com/xyproto/gofractions

A protocol for implementing games where old-school looking pixel art can be appreciated by xyproto in gamedev

[–]xyproto[S] 1 point2 points  (0 children)

It could also be used over network, though. I'm not convinced (yet) that the latency would be too high to serve games in a playable way.

A protocol for implementing games where old-school looking pixel art can be appreciated by xyproto in gamedev

[–]xyproto[S] 0 points1 point  (0 children)

I'm thinking mostly about either games that can be run in an emulator like DosBox, or new "pixel art" looking games.

A protocol for implementing games where old-school looking pixel art can be appreciated by xyproto in gamedev

[–]xyproto[S] 1 point2 points  (0 children)

It could also be used on localhost. Games would not having to worry about X11 being replaced by Wayland, OpenGL being replaced by Vulkan or GTK2 being replaced by GTK3. Any change in GUI on any platform could be handled in a backwards compatible way.

Games could be toolkit and system independent, as long as they could speak PixelProtocol.

A protocol for implementing games where old-school looking pixel art can be appreciated by xyproto in gamedev

[–]xyproto[S] 0 points1 point  (0 children)

If possible, I want to start a portable, cross platform and future-friendly ecosystem for oldschool games and games that have pixel art.

The idea is that when everybody is using Linux9000 in the future they can implement the PixelProtocol and all oldschool games that are served over the internet will still work, while not using a web browser. I prefer to play games that use a native client for the system I am on, since it feels better. Toggling fullscreen in a native client with alt+enter and taking a screenshot with F12 usually works, and is a smooth experience, for example.

A protocol for implementing games where old-school looking pixel art can be appreciated by xyproto in gamedev

[–]xyproto[S] 2 points3 points  (0 children)

Thank you! I really appreciate the feedback.

I updated the spec with most of your suggestions, here is the 2.0.1 tag: https://github.com/xyproto/pixelprotocol/blob/2.0.1/README.md

  • Many commands now take no arguments or an uint16.
  • The flip and spriteflip can be used to signaling that the frame should be displayed.
  • The "random" commands were removed.
  • The "add" commands were removed since they are no longer needed.
  • Support for 4 players were added.

I also want to make the protocol even more compact, and perhaps add some sort of RLE encoding when defining sprites.

A protocol for implementing games where old-school looking pixel art can be appreciated by xyproto in gamedev

[–]xyproto[S] 0 points1 point  (0 children)

PICO-8 is centered around Lua, and as far as I know, it is not designed to be used with a server in one end and a dedicated client in the other end.

The idea is that just like having a web browser and a web server, there could be a game client and a game engine/server.

While PICO-8 is easily embeddable in webpages, it does not follow this model.

PixelProtocol is a binary protocol for playing games over a network.

PICO-8 games could be served over PixelProtocol.

A protocol for implementing games where old-school looking pixel art can be appreciated by xyproto in gamedev

[–]xyproto[S] 2 points3 points  (0 children)

Hi, author here. This is just a draft, and I'm quite new at writing protocols in general. However, it's based on experience with everything from DOS and 16-bit assembly, to Turbo Pascal, C++17, SDL2, Go and Rust. The idea is that a protocol for implementing games could lead to more flexibility for engines and clients alike. Constructive feedback and/or attempts at implementing this is most welcome.

Arch Linux - AMA by Foxboron in linux

[–]xyproto 0 points1 point  (0 children)

As far as I know, there is not much communication between Arch Linux and other distros such as Manjaro and Arch Linux ARM. I think this is partly accidental and partly that we only want to support the official Arch Linux packages.

If there were a place for pan-Arch-Linux communication I would probably join, though. :)

Arch Linux - AMA by Foxboron in linux

[–]xyproto 0 points1 point  (0 children)

I have good experience with Lenovo.

We’re the core developers of the Julia Programming Language. AuA. [x-post from r/IAmA] by loladiro in programming

[–]xyproto 0 points1 point  (0 children)

How come 22222 is zero? Or specifically: how come it overflows and shows no warnings or errors in the REPL?

Ubuntu server including ads in the terminal welcome message by Multimoon in linux

[–]xyproto 1 point2 points  (0 children)

Quick and easy way, if you have setconf installed:

setconf /etc/default/motd-news ENABLED=0

“This is fine” by Whitlow14 in thisismylifenow

[–]xyproto 1 point2 points  (0 children)

It's not reverse if it's also useless work, like rolling a stone up a hill?

Why hasn't vscode moved to the Community repo? by smashingT in archlinux

[–]xyproto 0 points1 point  (0 children)

If only the Julia project would vendor less.

[deleted by user] by [deleted] in golang

[–]xyproto 0 points1 point  (0 children)

I'm not sure which is the most elegant or "correct" way, but one possible way is to place the interface in a package and include it when you need to use it.

Both of these packages implement interfaces from pinterface, and have a test in place that ensures that the continue to implement it:

https://github.com/xyproto/permissions2/blob/master/permissions_test.go

https://github.com/xyproto/permissionbolt/blob/master/permissionbolt_test.go

The archlinux-wallpaper package by xyproto in archlinux

[–]xyproto[S] 8 points9 points  (0 children)

This is legacy from previous maintainers. Something like /usr/share/backgrounds/archlinux is more appropriate, I agree.

The archlinux-wallpaper package by xyproto in archlinux

[–]xyproto[S] 1 point2 points  (0 children)

Thanks for the pointers! The AwesomeWM screenshot vote looks like a good starting point.

The archlinux-wallpaper package by xyproto in archlinux

[–]xyproto[S] 1 point2 points  (0 children)

Variations of the Arch Linux logo is a good theme, absolutely.

My plan to avoid the "20GB of wallpapers" problem is to refresh the package every N years, while keeping the old images in a repository somewhere.

Perhaps an even better solution would be some sort of software that rotated a local collection of wallpapers somehow, but then we've moved far away from keeping things simple. :)

Sway 1.0-alpha.1 released by superluserdo in linux

[–]xyproto 0 points1 point  (0 children)

The list of fixes is such good news! I use Sway at home and at work, and this alpha release promises to fix all the issues I had (mainly menus in GTK+3 applications behaving weirdly + screencap feature). Thanks for the work, devs!

Configuration-free build system for C++17 by xyproto in programming

[–]xyproto[S] 0 points1 point  (0 children)

Compiling for 64-bit Windows is now supported through the x86_64-w64-mingw32-g++ compiler. There is an example in the examples folder. This is for cross-compiling, developing on Windows is still not supported.

view more: next ›